On Mon, Jan 17, 2005 at 02:28:57AM -0700, Duncan wrote: > Daniel Ahlberg posted <[EMAIL PROTECTED]>, excerpted > below, on Mon, 17 Jan 2005 04:23:14 +0100: > > > TOP TEN: > > ======== > > > > games-mud/gMOO-0.4.8-r1 - 1081 days (~amd64) > > net-misc/smssend-3.2 - 1081 days (~sparc) > > x11-libs/buffy-0.2-r1 - 1081 days (~ppc) > > sci-chemistry/babel-1.6 - 1081 days (~amd64) > > app-office/gnofin-0.8.4 - 1081 days (~sparc) > > media-sound/id3-0.12-r1 - 1081 days (~ppc64) > > app-office/sc-7.12 - 1081 days (~amd64) > > dev-util/mergetrees-0.9.3 - 1081 days (~mips ~ppc) > > app-text/duconv-1.1 - 1081 days (~mips) > > sci-chemistry/moldy-2.16e - 1081 days (~ppcmacos) > > > > Questions and comments may be directed to [EMAIL PROTECTED] > > [posted to list and to aliz directly, as this is a reply to an automated > posting] > > OK, from previous discussion, we know that the script, due to portage, > can't tell how long an ebuild has actually been keyworded ~arch, if the > keyword was just added to the package (or something like that.. I may be > misunderstanding the details).
Portage might not be able to give you that information, but there is whole history of portage tree stored in CVS. Just find the commit that added an ~arch keyword (becomes a bit complicated to get the right one when package moved). Just out of curiosity: games-mud/gMOO-0.4.8-r1 is sitting in tree since Wed Sep 10 19:03:12 2003 UTC (16 months, 1 week ago) and was keyworded ~amd64 in revision 1.8 on Tue Dec 21 11:50:16 2004 UTC (3 weeks, 5 days ago). Regards, Peter Cech -- [email protected] mailing list
