I had an idea this morning about implementing glsa as a special set. I know the current portage code base is not ready for /etc/portage/sets support, but I thought it might be an easy way to integrate a glsa up/downgrades group (set) listing in portholes upgrades view (needs some familiarity of porthole's gui).
I was thinking that /etc/portage/sets/glsa could be a symlink to set list in the current metadata/glsa directory of the portage tree. That file should be relatively easy to auto-generate from the existing glsa*.xml files there already. Perhaps a FEATURES="GLSA_SET" would generate that file on completion of an "emerge --sync" I could also then put a GLSA field into porthole's package Summary view as well as a GLSA notebook page(s) to display the appropriate glsa?.xml file(s). What do you think of the idea? Then as portage/pkgcore gets sets support all anyone would need do is: # emerge -upv glsa (or any proper way emerge will handle set names) for a cli listing of packages needing attention. The one thing I can think of that would need slightly different handling from normal set parsing would be to only list those qualifying packages that are installed and ignore any other not installed package listed. -- Brian <[EMAIL PROTECTED]> -- gentoo-portage-dev@gentoo.org mailing list
