| 1 |
Hi, |
| 2 |
|
| 3 |
One can see some similarity to a thread around week or two old (about |
| 4 |
critical packages). I would imagine, that a simple and straightforward |
| 5 |
solution would be to make a new set of packages. Since we already have |
| 6 |
world and system sets, it wouldn't hurt to have a third, "safe" list |
| 7 |
which would be configurable by user. What I mean is: |
| 8 |
|
| 9 |
I consider ssh, postfix two very important packages (ssh is pretty |
| 10 |
stable, but hey, what if...) and I would most certainly not want to |
| 11 |
trigger emerge world and not notice postfix. So: I would add ssh and |
| 12 |
postfix to the "safe" set and do emerge -avu @safe, have a coffee and |
| 13 |
looked whether it's ok (mail are flowing, can login, etc. etc.) and |
| 14 |
then do emerge -avuD world and sleep well. |
| 15 |
|
| 16 |
I think this would be good solution for all of you? |
| 17 |
|
| 18 |
|
| 19 |
Regards Ladislav Laska |
| 20 |
S pozdravem Ladislav Laska |
| 21 |
--- |
| 22 |
xmpp/jabber: ladislav.laska@××××××.cz |
| 23 |
|
| 24 |
|
| 25 |
|
| 26 |
On Sun, Oct 18, 2009 at 2:10 AM, Duncan <1i5t5.duncan@×××.net> wrote: |
| 27 |
> Patrick Lauer posted on Sat, 17 Oct 2009 09:53:39 +0200 as excerpted: |
| 28 |
> |
| 29 |
>> On Saturday 17 October 2009 01:29:00 Daniel Bradshaw wrote: |
| 30 |
>>> Some packages, like findutils, are pretty robust and generally just get |
| 31 |
>>> on with working. |
| 32 |
>>> Other packages, like apache and ssh, need are more fragile and need |
| 33 |
>>> plenty of configuration. |
| 34 |
>> That's almost completely user-side configuration outside the influence |
| 35 |
>> of portage. emerge findutils and emerge apache "works" the same ... |
| 36 |
>> |
| 37 |
>> |
| 38 |
>>> Packages from the second group want emerging on their own, or in small |
| 39 |
>>> groups, the better to keep an eye out for notices about things that |
| 40 |
>>> might break, to update configs, and to check that they're running |
| 41 |
>>> happily. |
| 42 |
>> That's a very individual thing :) |
| 43 |
>> Sometimes apache is a critical service, sometimes apache is just there |
| 44 |
>> as a fallback if/when the lighttpd+php+... stack breaks. |
| 45 |
> |
| 46 |
> FWIW, there's a portage helper package, IDR the name as I have my own |
| 47 |
> system for this but it looks like it might be helpful here, that allows |
| 48 |
> users to pick and choose their updates. One could run it multiple times, |
| 49 |
> updating (what the user considers) the critical stuff on its own, and |
| 50 |
> updating everything else in a big bunch. |
| 51 |
> |
| 52 |
> That seems like the answer here; it already exists; and it's in the tree |
| 53 |
> (unless it has been removed recently, I don't know as IDR the name). |
| 54 |
> Take a look thru app-portage and see what you find. |
| 55 |
> |
| 56 |
> -- |
| 57 |
> Duncan - List replies preferred. No HTML msgs. |
| 58 |
> "Every nonfree program has a lord, a master -- |
| 59 |
> and if you use the program, he is your master." Richard Stallman |
| 60 |
> |
| 61 |
> |
| 62 |
> |
Archives