version control - Best practice for using one mercurial project in another -

version control - Best practice for using one mercurial project in another -

what best practices using 1 mercurial project in another? i've got django app i'm working on, i'm using mercurial version command website uses app. i've looked @ mercurial subrepositories, apparently considered "feature of lastly resort". there way of doing want do, or have re-create code app website repo when want update new version of app?

in specific case allow pip handle django application dependencies: http://guide.python-distribute.org/pip.html#installing-from-a-vcs

we have in our "website" repo requirements.txt , our deploy pip install --upgrade -r requirements.txt pulls latest repo , installes application's virtual env. gives nice flexibility , separation while leaving bundle management pip. vcs urls in pip can point specific tag or branch if want different sites using different revisions same underlying repo.

pip has -e /path/to/file mode pointing "editable" clone that's outside website repo, work too, i've not tried it.

that said, if think subrepos fit workflow improve means utilize them. work fine, people hung on workflow constraints ("what mean can't commit parent repo w/o committing in subrepo?!")

version-control mercurial mercurial-subrepos