public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev]  Re: New ebuild metadata to mark how robust the 	package is?
Date: Mon, 26 Oct 2009 21:49:26 +0000 (UTC)	[thread overview]
Message-ID: <pan.2009.10.26.21.49.26@cox.net> (raw)
In-Reply-To: 255f067f0910260555r32f2d1ccxdcf6e182e6c57ea1@mail.gmail.com

Ladislav Laska posted on Mon, 26 Oct 2009 13:55:51 +0100 as excerpted:

> 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?

Yes.  Sets were left for 2.2, as the implementation wasn't quite ready 
for 2.1 stability.  (As I understand it, there's multiple set 
implementations, and before sets become available as in-tree kde install 
options, for instance, they needed some reconciliation and possible PMS/
EAPI approval.)

-- 
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




      reply	other threads:[~2009-10-26 21:50 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
2009-10-26 21:49               ` Duncan [this message]

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=pan.2009.10.26.21.49.26@cox.net \
    --to=1i5t5.duncan@cox.net \
    --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