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