public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Karsten Schulz <kaschu@t800.ping.de>
To: Marius Mauch <genone@genone.de>, gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] RFC: security updates only? (security-1.0.ebuild)
Date: Mon, 18 Aug 2003 12:29:59 +0200	[thread overview]
Message-ID: <200308181229.59037.kaschu@t800.ping.de> (raw)
In-Reply-To: <20030816213804.267fee26.genone@genone.de>

Am Samstag, 16. August 2003 21:38 Marius Mauch wrote:
> I don't know how many people actually tested my stuff
> (http://gentoo.devel-net.org/glsa/ in case you haven't seen it) so I'll
> explain how it works:

I did :-)

> So, what is needed to get this working?
> - put the GLSA in a standard location for automated retrieval, I suggest
> both in the rsync tree and somewhere on www.gentoo.org
> - convert all GLSA into XML format, this could be done by the authors or
> a converter script
> - some code additions, nothing major
> - a lot of testing :)

I would like to discuss some aspects of your software. I like it, and I think, 
it could make admin's life easier. 

First, for what reason do you maintain /var/cache/edb/glsa? You could ask 
portage to see, wether a special version of a package is installed in the 
system or is not. To store applied GLSAs in this file seems redundant to me, 
isn't it?

Second, the 'glsa-' prefix of the GLSA filenames seems unnecessary to me. The 
GLSA information is stored in the directory /usr/portage/glsa/. Why not name 
the file with its unique GLSA identifier (200307-07 or perhaps 
200307-07.xml), shouldn't that be enough?

In your 'readme' file you wrote, that there is no installation needed. 
Nevertheless I would provide a little install-script, which checks the 
presence of the needed files and directories (/etc/portage/, 
/usr/portage/glsa/  and /var/cache/edb/glsa). Without this dirs and the file, 
glsa.py fails.

Please feel free to contact me for further testing!

have fun!
Karsten



--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2003-08-18 10:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-16  9:46 [gentoo-dev] RFC: security updates only? (security-1.0.ebuild) Karsten Schulz
2003-08-16 10:20 ` Paul de Vrieze
2003-08-16 11:03   ` Karsten Schulz
2003-08-16 11:19     ` Karsten Schulz
2003-08-16 14:31     ` Paul de Vrieze
2003-08-16 15:56       ` Klavs Klavsen
2003-08-16 16:18         ` Karsten Schulz
2003-08-16 15:59       ` Karsten Schulz
2003-08-16 17:11         ` Paul de Vrieze
2003-08-16 19:38           ` Marius Mauch
2003-08-18 10:29             ` Karsten Schulz [this message]
2003-08-18 19:17               ` Marius Mauch

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200308181229.59037.kaschu@t800.ping.de \
    --to=kaschu@t800.ping.de \
    --cc=genone@genone.de \
    --cc=gentoo-dev@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox