Gentoo Archives: gentoo-dev

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

Replies