I sometimes use libraries or other collateral code that needs to be coordinated with the Drupal code but shouldn't be accessible within the web tree. For that reason all of the projects I work on have the drupal tree in `/webroot/[drupal-stuff]` instead of the regular old `/[drupal-stuff]` that a lot of people use.

It would be *great* if gsb didn't make assumptions about where in the repository you'd like Drupal itself to be.

Comments

sdboyer’s picture

sdboyer commented
Project: » dog (Drupal on Git)

I've agonized quite a bit over this, and settled on the fact that GSB (now dog - I've changed the project accordingly on this issue) is, in the immediate term, best served if it ties itself tightly to the drupal root.

More a bit later, but I needed to move this issue so it didn't disappear when I deleted gsb :)

sdboyer’s picture

sdboyer commented
Title: GSB - Allow Drupal code to be placed in a sub-directory » Allow Drupal code to be placed in a sub-directory
tizzo’s picture

tizzo commented
Status: Active » Closed (won't fix)

This is a terrible idea and Sam was very patient with me explaining the why.

Git doesn't allow you to place a submodule inside of a submodule. If you want to place things like modules in the sites/*/modules dirs and you want to pull changes from up stream, those need to be submodules. If Drupal itself is a submodule you can't add a submodule inside the drupal directory inside your repository root without creating a fork of Drupal somewhere and adding your submodules to that. In short, it's going to be a huge nightmare of unnecessarily nested git repositories.

We should never, ever, support this feature.