From mboxrd@z Thu Jan 1 00:00:00 1970
Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org)
by finch.gentoo.org with esmtp (Exim 4.60)
(envelope-from <gentoo-dev+bounces-38160-garchives=archives.gentoo.org@lists.gentoo.org>)
id 1N0e4a-0000JL-B9
for garchives@archives.gentoo.org; Wed, 21 Oct 2009 16:30:04 +0000
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id 23614E081C;
Wed, 21 Oct 2009 16:30:03 +0000 (UTC)
Received: from cdptpa-omtalb.mail.rr.com (cdptpa-omtalb.mail.rr.com [75.180.132.121])
by pigeon.gentoo.org (Postfix) with ESMTP id 022FEE081C
for <gentoo-dev@lists.gentoo.org>; Wed, 21 Oct 2009 16:30:02 +0000 (UTC)
Received: from linux1.localdomain ([76.183.49.63])
by cdptpa-omta01.mail.rr.com with ESMTP
id <20091021163002304.ITPY3542@cdptpa-omta01.mail.rr.com>
for <gentoo-dev@lists.gentoo.org>;
Wed, 21 Oct 2009 16:30:02 +0000
Received: by linux1.localdomain (Postfix, from userid 1000)
id DEE6343C03; Wed, 21 Oct 2009 11:30:01 -0500 (CDT)
Date: Wed, 21 Oct 2009 11:30:01 -0500
From: William Hubbs <williamh@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: New ebuild metadata to mark how robust the
package is?
Message-ID: <20091021163001.GA16175@linux1>
Mail-Followup-To: gentoo-dev@lists.gentoo.org
References: <1255733421-30950-mlmmj-4f4db363@lists.gentoo.org>
<7486f8688d881f8d4a987199cb9ec8ea.squirrel@core-mail.net>
<200910170953.40078.patrick@gentoo.org>
<pan.2009.10.18.00.10.51@cox.net>
<255f067f0910210545u5790cdccxaaa2f390a6493496@mail.gmail.com>
<255f067f0910210821m68ef25b0q89bdbe2083c4425b@mail.gmail.com>
Precedence: bulk
List-Post: <mailto:gentoo-dev@lists.gentoo.org>
List-Help: <mailto:gentoo-dev+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-dev+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-dev+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-dev.gentoo.org>
X-BeenThere: gentoo-dev@lists.gentoo.org
Reply-to: gentoo-dev@lists.gentoo.org
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="bg08WKrSYDhXBjb5"
Content-Disposition: inline
In-Reply-To: <255f067f0910210821m68ef25b0q89bdbe2083c4425b@mail.gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
X-Archives-Salt: 34aa2593-b43b-4cff-b62e-424db3c2f188
X-Archives-Hash: 07627b207e4be39b548dd10bd4102d40
--bg08WKrSYDhXBjb5
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Afaik, you can already do this.
Make a file in /etc/portage/sets/critical, or whatever you want to call
it, and in there list the packages you are concerned about.
Then you can do:
emerge -NDup @critical
to see the packages in that set that need to be upgraded or you can use
@critical in any other place you could use a set.
William
On Wed, Oct 21, 2009 at 03:21:34PM +0000, Ladislav Laska wrote:
> Of course, by "safe" I meant "unsafe" or "needs-additional-care" or
> whatever,... My bad.
>=20
> Regards Ladislav Laska
> S pozdravem Ladislav Laska
> ---
> xmpp/jabber: ladislav.laska@jabber.cz
>=20
>=20
>=20
> On Wed, Oct 21, 2009 at 12:45 PM, Ladislav Laska
> <ladislav.laska@gmail.com> wrote:
> > Hi,
> >
> > One can see some similarity to a thread around week or two old (about
> > critical packages). I would imagine, that a simple and straightforward
> > solution would be to make a new set of packages. Since we already have
> > world and system sets, it wouldn't hurt to have a third, "safe" list
> > which would be configurable by user. What I mean is:
> >
> > I consider ssh, postfix two very important packages (ssh is pretty
> > stable, but hey, what if...) and I would most certainly not want to
> > trigger emerge world and not notice postfix. So: I would add ssh and
> > postfix to the "safe" set and do emerge -avu @safe, have a coffee and
> > looked whether it's ok (mail are flowing, can login, etc. etc.) and
> > then do emerge -avuD world and sleep well.
> >
> > I think this would be good solution for all of you?
> >
> >
> > Regards Ladislav Laska
> > S pozdravem Ladislav Laska
> > ---
> > xmpp/jabber: ladislav.laska@jabber.cz
> >
> >
> >
> > On Sun, Oct 18, 2009 at 2:10 AM, Duncan <1i5t5.duncan@cox.net> wrote:
> >> Patrick Lauer posted on Sat, 17 Oct 2009 09:53:39 +0200 as excerpted:
> >>
> >>> On Saturday 17 October 2009 01:29:00 Daniel Bradshaw wrote:
> >>>> Some packages, like findutils, are pretty robust and generally just =
get
> >>>> on with working.
> >>>> Other packages, like apache and ssh, need are more fragile and need
> >>>> plenty of configuration.
> >>> That's almost completely user-side configuration outside the influence
> >>> of portage. emerge findutils and emerge apache "works" the same ...
> >>>
> >>>
> >>>> Packages from the second group want emerging on their own, or in sma=
ll
> >>>> groups, the better to keep an eye out for notices about things that
> >>>> might break, to update configs, and to check that they're running
> >>>> happily.
> >>> That's a very individual thing :)
> >>> Sometimes apache is a critical service, sometimes apache is just there
> >>> as a fallback if/when the lighttpd+php+... stack breaks.
> >>
> >> FWIW, there's a portage helper package, IDR the name as I have my own
> >> system for this but it looks like it might be helpful here, that allows
> >> users to pick and choose their updates. ??One could run it multiple ti=
mes,
> >> updating (what the user considers) the critical stuff on its own, and
> >> updating everything else in a big bunch.
> >>
> >> That seems like the answer here; it already exists; and it's in the tr=
ee
> >> (unless it has been removed recently, I don't know as IDR the name).
> >> Take a look thru app-portage and see what you find.
> >>
> >> --
> >> Duncan - List replies preferred. ?? No HTML msgs.
> >> "Every nonfree program has a lord, a master --
> >> and if you use the program, he is your master." ??Richard Stallman
> >>
> >>
> >>
> >
>=20
--=20
William Hubbs
gentoo accessibility team lead
williamh@gentoo.org
--bg08WKrSYDhXBjb5
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.11 (GNU/Linux)
iEYEARECAAYFAkrfNwkACgkQblQW9DDEZTg5igCgnkqSv3BgA3zNsOySRhYnM/92
4fUAn1CoMSyONk+LKRhSyFM420EjJyni
=o2R3
-----END PGP SIGNATURE-----
--bg08WKrSYDhXBjb5--