Re: SCM for packages

Dropping David, who can pick up the thread on -beta if he wants to. Mats Lidell writes: This is a bad idea. Bazaar has this feature, they call it "lightweight checkouts". It adds a lot of complexity to the implementation, and what is worse, it seems to confuse users. Basically, not worth it for the purpose of casual checkouts. (Developers use it because it's the only way to share the repo in Bazaar, and they have pretty sucky space efficiency, so it ends up saving a lot of space if you have multiple branches checked out.) And unnecessary, IMO. As Mike points out, Mercurial history storage really is efficient. Here's a du for my current XEmacs workspace, with almost 4500 changesets: chibi:xemacs steve$ du -sk . .hg ./+* 230868 . 12296 .hg 4 .hgignore 12 .hgtags 51096 ./+build 41860 ./+gtk chibi:xemacs steve$ find . -name '*.elc' | xargs du -ck 4664 total chibi:xemacs steve$ find . -name '*.info' | xargs du -ck 964 total So the working tree takes up 110 MB (13MB of Lisp), C build products 40~50MB per build, Lisp and Info build products about 5MB per build, and Mercurial repo data only about 12MB. I don't see any reason why the packages would show a metadata ratio of as much as 20% of the source tree, while build products run about 40% for Lisp. Surely that's acceptable? _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta