Michael Sperber <sperber(a)deinprogramm.de> writes:
Well, the idea is that you only fiddle with indidvidual packages
you're doing development on them - that's when the subrepos really help.
Mercurial does manage a consistent state for the package
subrepositories, much as a single repository would. So when you're just
trying to build, you should pull all packages.
I am only wondering if it is worth the effort. A package author ought to
build before pushing any changes. This means that developers will most
likely pull everything anyway. Pushing individual packages might mean
that "insignificant" changes in other packages get lost leading to
build-bot errors and more commits. Errors due to changes in other
packages won't manifest until someone builds/uses with up-to-date
versions of both.
The large repo size is a first-time issue only, I guess.
But hey, I don't want to stop anyone.
XEmacs-Beta mailing list