On Friday 21 April 2006 17:18, D Bera wrote: > On Friday 21 April 2006 18:10, Pat Double wrote: > > On Friday 21 April 2006 17:02, D Bera wrote: > > > Pat, I changed FilterEbuild to derive from FilterPackage. Nothing > > > should be broken since I didnt change any functionality and I tested it > > > on 2 simple ebuilds. But you might want to go through it once to make > > > sure I didnt drop anything in copy/paste. I dont know the ebuild format > > > good enough. > > > > > > - dBera > > > > Will do. I don't know if the Deb and RPM filters put in installation info > > into the properties, but if so I also have a patch to the ebuild filter > > to do so. It would be nice to standarize on those properties like the > > size of the installed files, when it was installed, etc. > > For RPM, I try to extract the information that is useful for searching or > displaying. I didnt feel filesizes would be useful to extract so I didnt. > Its upto you for the ebuild filter. But since filesizes can be only be > extracted from "installed"-ebuilds and not ebuilds lying in the > file-system, and I am not sure how can it be used while displaying in > beagle-search, I am not too keen on adding that information to > FilterPackage. Just add them specific to FilterEbuild. > > - dBera The way Gentoo works is that an installed ebuild is copied into another location. So the installation info only occurs if the crawl is on the installation database /var/db/pkg, which contains a copy of the ebuild. The proposed change detects if the the ebuild file is installed (by the presence of a CONTENTS file) and then adds the info. If ebuilds were like RPM I think a queryable would be more in order. As far as seeing the results, it's just another property to show. Nice for the user I suppose. I have a kerry patch that shows install time and size. -- Pat Double, pat patdouble com "In the beginning God created the heaven and the earth."
Attachment:
pgpJ7zAFrB3pM.pgp
Description: PGP signature