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. > > Regards Ladislav Laska > S pozdravem Ladislav Laska > --- > xmpp/jabber: [email protected] > > > > On Wed, Oct 21, 2009 at 12:45 PM, Ladislav Laska > <[email protected]> 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: [email protected] > > > > > > > > On Sun, Oct 18, 2009 at 2:10 AM, Duncan <[email protected]> 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 small > >>>> 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 times, > >> 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 tree > >> (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 > >> > >> > >> > > > -- William Hubbs gentoo accessibility team lead [email protected]
pgpDnIvpt92jl.pgp
Description: PGP signature
