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: Keyword policy for non standard things
Date: Wed, 22 Oct 2008 21:12:28 +0000 (UTC)	[thread overview]
Message-ID: <pan.2008.10.22.21.12.28@cox.net> (raw)
In-Reply-To: 20081022172853.41878802@terra.solaris

Christian Faulhammer <opfer@gentoo.org> posted
20081022172853.41878802@terra.solaris, excerpted below, on  Wed, 22 Oct
2008 17:28:53 +0200:

> no support in stable profile out-of-the-box -> no stable keyword ->
> INVALID request.  No compromise.

Well, at least the one referenced bug (243050) is for an ~arch keyword, 
not a stable keyword.  That's different, as the ~arch keyword is useful 
for saying yes, it has been tested and is known to be workable on that 
particular arch in /some/ form, even if it's not (and may never be) 
stable.  x86 many not have to worry about that, but the other archs do.

But mentioning that it can never be stabilized (and referring to a policy 
URL for why) in the package description would still be good, as would 
mention of the fact that yes, it does require user application of patches 
elsewhere.

-- 
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:[~2008-10-22 21:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-21 23:41 [gentoo-dev] Keyword policy for non standard things Dawid Węgliński
2008-10-22  9:54 ` Alistair Bush
2008-10-22 10:43   ` Dawid Węgliński
2008-10-22 15:28 ` [gentoo-dev] " Christian Faulhammer
2008-10-22 21:12   ` 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.2008.10.22.21.12.28@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