While reviewing the logs for some recent ebuilds, I found the following line: /usr/sbin/ebuild.sh: line 1: /usr/lib/portage/bin/pkglist: No such file or directory The src_install() function in grsecurity-base-policy-20030614.ebuild contains the offending reference to pkglist, which seems to have been absent from portage for about two months. The soon-to-be-attached patch to grsecurity-base-policy-20030614.ebuild duplicates the required functionality. Somebody with a better understand of portage will want to look at this. I don't think I broke any rules by skimming /var/db/pkg directly, but I also don't know of any "right way" to accomplish the same thing from a single ebuild.
Created attachment 28933 [details, diff] duplicates functionality of pkglist within ebuild
Brad (grsec author) is about to push grsec2 to stable. The only that holds it back is the lack of documentaion. I'm thinking along the lines of grsecurity-base-policy should be obsoleted and or removed from portage. Objections?
Makes sense, as soon as nothing else in portage uses the existing grsecurity code, but in the meantime...
grsecurity-base-policy has been removed from the tree.
