public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ladislav Laska <ladislav.laska@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: New ebuild metadata to mark how robust the  package is?
Date: Mon, 26 Oct 2009 13:55:51 +0100	[thread overview]
Message-ID: <255f067f0910260555r32f2d1ccxdcf6e182e6c57ea1@mail.gmail.com> (raw)
In-Reply-To: <20091021163001.GA16175@linux1>

This is awesome! It really like the idea, but (there is always "but",
right?) it doesn't work.

I have googled for it for a while and haven't found any reference how
to do it exactly.

I have created mentioned file and run emerge, but I've got

$ sudo emerge -av @critical
!!! '@critical' is not a valid package atom.
!!! Please check ebuild(5) for full details

And I have no idea why. Also, I'm using portage 2.1.7.1. I guess this
is new feature in 2.2?

Regards Ladislav Laska
S pozdravem Ladislav Laska
---
xmpp/jabber: ladislav.laska@jabber.cz



On Wed, Oct 21, 2009 at 5:30 PM, William Hubbs <williamh@gentoo.org> wrote:
> 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: ladislav.laska@jabber.cz
>>
>>
>>
>> On Wed, Oct 21, 2009 at 12:45 PM, Ladislav Laska
>> <ladislav.laska@gmail.com> 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: ladislav.laska@jabber.cz
>> >
>> >
>> >
>> > On Sun, Oct 18, 2009 at 2:10 AM, Duncan <1i5t5.duncan@cox.net> 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
> williamh@gentoo.org
>



  reply	other threads:[~2009-10-26 12:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1255733421-30950-mlmmj-4f4db363@lists.gentoo.org>
2009-10-16 23:29 ` [gentoo-dev] New ebuild metadata to mark how robust the package is? Daniel Bradshaw
2009-10-16 23:48   ` Jeremy Olexa
2009-10-17  0:50   ` [gentoo-dev] " Ryan Hill
2009-10-17  5:33   ` [gentoo-dev] " Rémi Cardona
2009-10-17  9:27     ` Tobias Klausmann
2009-10-17  9:47       ` Petteri Räty
2009-10-17  7:53   ` Patrick Lauer
2009-10-18  0:10     ` [gentoo-dev] " Duncan
2009-10-21 12:45       ` Ladislav Laska
2009-10-21 15:21         ` Ladislav Laska
2009-10-21 16:30           ` William Hubbs
2009-10-26 12:55             ` Ladislav Laska [this message]
2009-10-26 21:49               ` Duncan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=255f067f0910260555r32f2d1ccxdcf6e182e6c57ea1@mail.gmail.com \
    --to=ladislav.laska@gmail.com \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox