On Feb 8, 2005, at 00:45, Duncan wrote:
The idea for the script is good, but barring portage support for tracking
the introduction of specific keywords, or barring a script intelligent
enough to go digging thru changelogs and the like, successfully parsing
them to find the missing data, the top-10 is always (well, for some
serious period into the future, anyway) going to be entirely a bunch of
noise, no signal, since there will always be more than 10 ebuilds where
an ~arch keyword was added long after the ebuild itself debuted.
Wouldn't the simple brute-force solution be to take a (daily || bi-daily || weekly || bi-weekly ) snapshot of the tree, store all current keywords for all current ebuilds in the tree, and repeat for several iterations. This way we have a history of ebuild/keyword/date tuples.
Perhaps I'll begin work on this during my more boring bioinformatics class.
-- Hasan Khalil Ebuild/Porting Co-Lead Gentoo for Mac OS X
PGP Key: 0x707B8F18 on pgp.mit.edu
PGP.sig
Description: This is a digitally signed message part
