According to Alfred M. Szmidt: > directories (same here). gcc would be far more managable with arch if > it was split into smaller bits (c-testsuite, c, objc, java, ada, > ada-testsuites, ...).
configs breaks the one changeset for the whole tree. A changeset can only contain modifications with a given c--b--v. That means that if 1. you need to "tla cat-config | xargs tla commit" (which sucks and is slow) and 2. you'll get as many unrelated changesets as you have configs (which sucks even more). configs are not the way to manage big trees, they are a minimalist workaround (and not a satisfying one at that). This is what made me stop using tla1/baz (even though baz is faster by caching more). The whole c--b--v business is nice at first sight but tla/baz are too slow for big trees and configs are not the way to fix it. Another gripe of mine: you can only branch c--b--v, not the tree "created" by a config so you must also iterate when branching. Don't make me wrong, I've been a very satisfied user of tla/baz for more than two years but these problems are getting too much. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- [EMAIL PROTECTED] Darwin snuadh.freenix.org Kernel Version 7.9.0: Wed Mar 30 20:11:17 PST 2005 _______________________________________________ Gnu-arch-users mailing list [email protected] http://lists.gnu.org/mailman/listinfo/gnu-arch-users GNU arch home page: http://savannah.gnu.org/projects/gnu-arch/
