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