On Sun, 23 Apr 2006 08:55:58 -0700 Brian <[EMAIL PROTECTED]> wrote: > 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).
Too complicated. First you currently need gentoolkit for glsa.py, and portage shouldn't depend on gentoolkit. Also you can't store system-specific files in the tree. And finally using an intermediate file creates some additional issues (check for IO/FS problems, checking permissions, etc). Any reason you need a real file for this instead of just generating the list on the fly? Just check glsa-check how to do that, it's not much more than a wrapper for glsa.py. Marius -- Public Key at http://www.genone.de/info/gpg-key.pub In the beginning, there was nothing. And God said, 'Let there be Light.' And there was still nothing, but you could see a bit better.
signature.asc
Description: PGP signature
