public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Stefan Boresch <stefan@mdy.univie.ac.at>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] making %95 of users happy
Date: Thu, 18 Apr 2002 21:28:40 +0200	[thread overview]
Message-ID: <20020418192840.GA8637@mdy.univie.ac.at> (raw)
In-Reply-To: <NCEBJBHELIGGHDDGAEGNIEENDJAA.wylie@geekasylum.org>

Please look to the end of this mail why I am cross-posting to
gentoo-security.

On Fri, Apr 19, 2002 at 04:29:52AM +1000, Todd Wright wrote:
> 
> And to the person (Andrew I think) who quoted the following from the gentoo site as a reason for not having release branches...
> 
> "*Portage allows you to set up Gentoo Linux the way you like it*..."
> 
> It doesnt. Just when I get it how I like it, it changes.

Great line -- I was going to write a lengthy reply to Andrew's mail,
but you put it in one line exactly. (And nailing with =< in
/var/cache/edb/world, while a great step in the right direction, isn't
sufficient; I totally agree!)

Here is my suggestion/wish:

Could one not create an --update security target to emerge.  This would
always do --update system, plus check for any updates of installed
packages (probably without consulting the edb/world file, or rather
counterchecking against it (*)) that are "earmarked" security relevant.
If such a beast existed, I could put a cron job calling 
emerge --update security -buildpkg
on my test machine, check every morning and distribute the binaries
to my network of 20+ workstations after quick tests that nothing serious
has been broken.

This target would give me the best of both worlds: Live on the
bleeding edge for my personal machine(s) [ which double as test
machines] and have something similar to a frozen major distribution
for the network where my boss, my students and collaborators try
to get their work done.

Oh, and I am happy to try contribute to following security alerts
and things like that.   Unfortunately, I haven't the least clue about
python, so I don't feel comfortable about writing --update security
myself.

Stefan

(*) If a user has nailed a package which has a potential
vulnerability, then the --update security target should yell
at him, but leave the responsibility with the administrator. That
would strike me as good Gentoo philosophy, doesn't it?

-- 
Stefan Boresch
Institute for Theoretical Chemistry and Structural Molecular Biology
University of Vienna, Waehringerstr. 17       A-1090 Vienna, Austria
Phone: -43-1-427752715                        Fax:   -43-1-427752790


  reply	other threads:[~2002-04-18 19:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-18 12:25 [gentoo-dev] making %95 of users happy Gaarde
2002-04-18 18:29 ` Todd Wright
2002-04-18 19:28   ` Stefan Boresch [this message]
2002-04-19  3:25     ` Fuper
2002-04-19 12:04       ` Todd Wright
2002-04-18 22:09         ` Sherman Boyd
2002-04-19 14:15         ` Fuper
2002-04-18 19:35   ` Terje Kvernes
2002-04-19  8:42     ` Paul de Vrieze
2002-04-19  9:44       ` Terje Kvernes
2002-04-19 10:19         ` Einar Karttunen
2002-04-19 11:34           ` Mike Payson
  -- strict thread matches above, loose matches on Subject: below --
2002-04-19 17:57 Gaarde
2002-04-20  0:30 ` John White
2002-04-20 18:26 Gaarde

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=20020418192840.GA8637@mdy.univie.ac.at \
    --to=stefan@mdy.univie.ac.at \
    --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