On Tue, Aug 26, 2008 at 04:57:50PM -0500, Yuri Vasilevski wrote: > > Why do you need to identify the changes? Considering that the checksum > > changes as well, is detecting change not sufficient? (or asking the > > VCS for what files have changed since your last check time). > I am writing a tool that creates deb (as in Debian package format) based > distributions from gentoo packages and that tool encodes the CVS > revision as part of "debian revision" of the packages. So I need this > part to be chronologically ordered, as opposed to have only the > knowledge of whenever the file has changed or not. I'd call that critically dangerous in missing some changes. If I have a file in $FILESDIR, and change it, but it has the same name, there is no commit to the ebuild, and your .debs won't pick up changes at all. This is usually for cases with compile fixes that don't need revision bumps at all, but sometimes there are also changes to scripts.
If you're making binary package .debs, I gather that you are grabbing the (pre|post)(inst|rm) and setup blocks for inclusion? That is an interesting use case, and would that would present a problem with any VCS migration. - Under SVN, you'd only have the global revision, which might not uniquely identify the file. - Bzr doesn't support keyword expansion in any released version. There are/were plans for it in 1.7, but I haven't seen anything since the first prototype. - Hg supports it with an extension: http://www.selenic.com/mercurial/wiki/index.cgi/KeywordExtension But has warnings about why it sucks http://www.selenic.com/mercurial/wiki/index.cgi/KeywordPlan See the 'keyword update intervals' item (mainly having to touch every file in the repo sometimes). - Git supports only the $Id$ keyword, and expands it to the SHA1 of the file, which ends up being a duplicate of the information we have in the Manifest. -- Robin Hugh Johnson Gentoo Linux Developer & Infra Guy E-Mail : [EMAIL PROTECTED] GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85
pgp8kuyAJCBo9.pgp
Description: PGP signature
