this is in some cases screwed up:
Project drupal (7.0) downloaded to /home/xl/workspace/drugit-test/drupal-7.0. [107.35 sec, 5.73 MB] [success]
Calling chdir(/home/xl/workspace/drugit-test)
Executing: git rev-parse --git-dir
.git
Calling chdir(/home/xl/workspace/drugit-test)
Calling chdir(.)
Executing: git submodule add git://git.drupal.org/project-stable/drupal.git ome/xl/workspace/drugit-test/drupal-7.0
Initialized empty Git repository in /home/xl/workspace/drugit-test/ome/xl/workspace/drugit-test/drupal-7.0/.git/
| Comment | File | Size | Author |
|---|---|---|---|
| #8 | drush-1051324.patch | 1.19 KB | jonhattan |
| #7 | fixed1051324.patch | 1.32 KB | geek-merlin |
| #1 | 0001-fixed-1051324.patch | 1.05 KB | geek-merlin |
Comments
Comment #1
geek-merlinpatch in the air.
Comment #2
geek-merlinComment #3
moshe weitzman commentedComment #4
jonhattan@axel.rutz post the command you're running and the complete sequence. I need to figure out what's going on.
Also note you're generating patches in a way that `patch` command don't work AFAIK. I was able to apply it with `git apply`
Comment #5
geek-merlinoh thank you for your comment!
as for the patch: sorry, i am a bit git centered - memo to me: figure out the git-format-patch option to play fine with the patch command.
(i think it's just about removing the mail headers in the patch file)
and yes, i was quite unthorough in my report:
what happens:
* git rev-parse --git-dir spits out a relative path
* the script expects an absolute path to calc the git-submodule-add parameters
* so the submodule is not added correctly (second arg wrong, missing in this case)
inserting "realpath" in the right place solves that.
Comment #6
jonhattanSo I figured out you're preforming
The git_drupalorg package-handler is almost able to do this by accident: the intention for --gitsubmodule is to add drupal projects as submodules to the cloned drupal codebase. Performing the above usecase should be part of a vcs integration, not a package-handler thing. So I'm declined to fix this the other way by marking --gitsubmodule as an invalid option when the project to clone is drupal. Note also that with the fix in #1 we have this probably undesirable scenario:
What do think maintainers and git-trained folks?
Comment #7
geek-merlini'm not so sure we're on the same construction area - i'll elaborate:
the problem arises when the output is NOT an absolute path (first case)
which showed ma that i had to fix my fix, see attached.
ps:
as for "drupal core as submodule" - this is my main use case, i'm heavily working on this and show you soon.
but that's another issue and will be told another time.
Comment #8
jonhattanI also hit what you explicit in #7 but didn't elaborate because if we supress --gitsubmodule when the project is drupal we avoid this case. Anyway I also found an alternative solution :)
Comment #9
geek-merlinyours is so much sexier!
worksforme.
Comment #10
moshe weitzman commentedif it works for you two, then in it goes.
Comment #11
jonhattanSo commited.
Comment #12
jonhattanComment #13
msonnabaum commentedBackported.
http://drupal.org/cvs?commit=501888