Danny van Dyk wrote: >> In practice I find it's rare that a user has been hacking around in >> the eclasses. All the SHA1 tells you is that it's not the most >> recent, but it's not easy to determine from the SHA1 exactly which >> version they do have (so it's not enough to determine what's >> different). >> >> Having said that, the most accurate way to find out what they have is >> to get them to attach the eclass and diff it yourself. However >> relying on the SHA1 also means you can't just say things like, "Check >> eclass <blah> is version 1.836 (look at the "$Header" line at the top >> of the file)." > > In the case of GIT you can just use 'git diff SHA1SUM' to see what has > changed or 'git log SHA1SUM..HEAD' to show a list of revisions in > between. So _if_ we changed to git, this would be no problem as long as > every user has sha1sum installed [which is part of coreutils]. > Well since that appears to be some way off, is there any way to get the needed functionality (version string inside ebuild) without a double commit? (Did i read that right?) I'm thinking at worst someone might have to add something to repoman, or a hook on the server end.
-- [EMAIL PROTECTED] mailing list
