Currently drush make supports a --working-copy option. This instructs any version control checkouts to maintain the checkouts as a working copy which can be independently managed (Updated etc.). However, this is an "all or nothing" approach.
It would be helpful if you could specify particular items to maintain working copies of without having to have it on for everything (Our example is we're basing the core install on a git checkout of pressflow which we *don't* want to keep the whole clone of, but some locally developed modules which we *do* want to keep as working copies).
The attached patch means that makefiles can provide a [download][working-copy] flag to specify that a project should maintain a working copy of that item, e.g.
projects[foo][type] = "module"
projects[foo][download][type] = "git"
projects[foo][download][url] = "ssh://git@gitrepo.example.com/foo.git"
projects[foo][download][working-copy] = "true"Running such a makefile through drush make *without* the --working-copy flag means that any projects that don't specify the [working-copy] flag will be non-working copies, but projects that do specify it will be kept as working copies.
| Comment | File | Size | Author |
|---|---|---|---|
| drush.patch | 2.72 KB | leewillis77 |
Comments
Comment #1
leewillis77 commentedI also have a similar patch for drush make 6.x-2.x as well - here: https://gist.github.com/1902076
Comment #2
joestewart commentedThanks. See these previous issues #1206340: introduce an options array in the root level of the makefile and #958844: PATCH: Allow [working-copy] in makefile as well as on commandline.
Can you look at #1206340: introduce an options array in the root level of the makefile and help get it finished?
Comment #3
leewillis77 commentedThere's a revised patch on #1206340: introduce an options array in the root level of the makefile, so we can probably close this issue?
Comment #4
moshe weitzman commentedBased on the title of that issue, it sounds not like a dupe. This is about per project control and that one is about control for a whole makefile.
Comment #5
joestewart commented@Moshe - I think it mostly comes from this comment - http://drupal.org/node/958844#comment-4795666
I suggested getting #1206340: introduce an options array in the root level of the makefile committed as feature complete for its original scope - http://drupal.org/node/1206340#comment-4863900
Comment #6
joestewart commentedThe patch at #35 in #1206340: introduce an options array in the root level of the makefile passes the test for "Drush makefiles should be able to flag individual projects to keep as working copies" as described here.
Comment #7
moshe weitzman commentedOK, lets mark this as a dupe then.