--- xml/htdocs/proj/en/glep/glep-0014.html 2003/08/24 22:11:46 1.2 +++ xml/htdocs/proj/en/glep/glep-0014.html 2003/11/10 19:22:24 1.3 @@ -33,13 +33,13 @@
The GLSA format needs to be specified, I suggest using XML for that to simplify parsing and later extensions. See implementation for a sample DTD. The format has to be compatible with the update tool of course. If necessary a converter -tool or an editor could be written for people not comfortable with XML. -Every GLSA has to be GPG signed by the responsible developer, who has to be -a member of the security herd.+tool or an editor could be written for people not comfortable with XML (update: +a QT based editor for the GLSA format written by plasmaroo exists in the +gentoo-projects repository). Every GLSA has to be GPG signed by the responsible +developer, who has to be a member of the security herd.
A prototype implementation (including the update tool, a DTD and a sample -XMLified GLSA) exists at http://gentoo.devel-net.org/glsa/ . This GLEP is based -on that implementation, though it can be changed or rewritten if necessary. -According to portage developers there is also already some support for this in -portage.+XMLified GLSA) exists at http://gentoo.devel-net.org/glsa/ and in the +gentoo-projects/gentoo-security/GLSA repository. This GLEP is based +on that implementation, though it can be changed or rewritten if necessary.