Re: [gentoo-dev] RFC: security updates only? (security-1.0.ebuild)

[Karsten Schulz <kaschu@t800.ping.de>]

Am Samstag, 16. August 2003 16:31 Paul de Vrieze wrote:
> Well, for a user it works, but it does not work in terms of providing a
> cache. Normally a cache is built. One thing needed for that is that we can
> parse dependencies.

Oh, I see. As far as I understand now, it works in this way:
emerge rsyncs and then generates the cache in /var/vache/edb/dep.
At this time, no ebuild is executed as a script and therefore the dependencies 
cannot be calculated. That I did not know, thanks for enlighten me, Paul.

So, if I understand things right, it has to go this way:
On the rsync-Servers there should be a file containing GLSAs. This file 
contains for example the following lines:
VERSION	1.0
nfs-utils	>=nfs-utils-1.0.4
gnupg	>=gnupg-1.2.2-r1

*After* rsyncing, but *before* building the cache, emerge should create a 
statical version of app-admin/security/security-VERSION.ebuild with the 
dependencies corresponding to the current system and the correct version.
After creating this ebuild, the cache could be build and an emerge -p security 
will show the needed updates. That seems to me a few lines of python code and 
an introduction of the new GLSA file.

How is that?

Karsten





--
gentoo-dev@gentoo.org mailing list