Marcus Harnisch <marcus.harnisch(a)xemacs.org> writes:
Michael Sperber <sperber(a)deinprogramm.de> writes:
> Well, the idea is that you only fiddle with indidvidual packages when
> 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.
That's a misunderstanding, sorry for being unclear: Developers will want
to make changes in a single package - possibly a whole bunch of them -
and push those changes - and test them - *before* actually making them
available to the global set of packages. With subrepos, she doesn't
have to branch the entire repo for doing this, but can just make local
changes and commit those.
Cheers =8-} Mike
Friede, Völkerverständigung und überhaupt blabla
XEmacs-Beta mailing list