The download method in DrushMakeDownload_Hg just delete .hg directory right after cloning. Sometimes I want the actual repo intact, the case when doing development of install profile for example. It's only when packaging the final product we want it to produce a 'clean build'. I looked into the download method for CVS and it use working-copy option so why not allow this for hg as well ?
For example, I can do something like:-
$ drush make --working-copy test.make www
I'm not sure whether that was the intention of working-copy option in cvs download method but I think there must be some option to tell drush make to create exact clone of the repo.
Comments
Comment #1
k4ml commentedforgot to attach the patch.
Comment #2
Frando commentedNice. Was looking for something similar recently. The --working-copy option should be applied to git as well, though
Comment #3
k4ml commentedIncluded git and bzr. bzr not tested though.
Comment #4
dmitrig01 commentedPlease use ! instead of null.
Comment #5
k4ml commentedRevised patch.
Comment #6
dmitrig01 commentedComitted, thanks
Comment #8
blazindrop commentedI noticed that starting with the the beta7 release, hg integration was removed, but there was no associated issue or discussion (at least that I can find). Will this be readded in the future? I'm reopening this issue so someone coming across this issue will see that it was removed.
beta7 release notes are here: http://drupal.org/node/840554
Comment #9
dmitrig01 commentedUnless someone is willing to step up to write the integration and bring to be feature-compatible as the other VCS systems, and also write tests for it, it will not be added back.
Comment #10
dmitrig01 commentedI'm going to close this, but if anyone wants to add hg back they can feel free to open a new issue.
Comment #11
parsingphase commentedThis is a patch to add mercurial support back to drush make 2.3.
With the exception of branches, it's a feature match against the git support.
I will add tests shortly and hopefully support this officially.
Please drop me a line if there is a more appropriate issue re: mercurial support to file this against. Otherwise I'll open a new one.
Comment #12
parsingphase commentedFirst patch of tests. Obviously a lot more to do; anyone who knows any stable mercurial repositories for drupal modules etc is welcome to tell me about them so I can use them for testing, particularly if they contain internal branches (none of ours do).
Comment #13
parsingphase commentedSee http://drupal.org/node/1259770 for a ticket on replacing mercurial support.