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

On Mon, 18 Aug 2003 12:29:59 +0200
Karsten Schulz <kaschu@t800.ping.de> wrote:

> Am Samstag, 16. August 2003 21:38 Marius Mauch wrote:
> > 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. 

I'm currently writing a GLEP to adress the problem, so far the feedback
on my stuff has been very positive so I'm optimistic that it will be
accepted.

> 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?

Sometimes you might want to solve an issue in another way than
recommended or the test result could be wrong or you don't want to fix
the issue or ...

> 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?

That's open for discussion. FYI, the glsa- prefix can be
changed/disabled in /etc/portage/glsa.conf.

> 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.

Right now the tool is nearly useless as there are no XMLified GLSAs
available. It's only a prototype. Once the GLEP is accepted
I'll write an ebuild for it or ask carpaski to add it to the portage
package.

Marius

--
gentoo-dev@gentoo.org mailing list


      reply	other threads:[~2003-08-18 19:17 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
2003-08-18 19:17               ` Marius Mauch [this message]

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=20030818211711.2e2bd18a.genone@genone.de \
    --to=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