public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Drake Wyrm <wyrm@haell.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] GTK2 QT Theme
Date: Sun, 11 Jan 2004 03:34:52 -0800	[thread overview]
Message-ID: <20040111113452.GA19950@phaenix.haell.com> (raw)
In-Reply-To: <20040111085937.06f3d628.spider@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1198 bytes --]

On Sun, Jan 11, 2004 at 08:59:37AM +0100, in <20040111085937.06f3d628.spider@gentoo.org>, Spider <spider@gentoo.org> wrote:
...conversation about a proposed ebuild...
> as it is its crashy, check the reported gaim crashes due to the theme
> for example (yes. that was the 0.2 version).  as ~ is -not- a playground
> for broken packages or known buggy things I oppose the inclusion of this
> until it can be shown as to not crash applications.
This seems as good a place as any to mention one of my many
ideas. ...which are usually ignored, but I might have a good
one someday. How about a new KEYWORDS flag to mark known-crapulent
packages. Playing off the use of "~arch" (which I read as "maybe arch"),
use "!arch" (which could be read "not arch") to mark packages which are
somewhere between useless and alpha, but happen to be worth watching
and developing. It would also be a great way to move the hard-masking
features of packages.mask into the relevant ebuild. Looks like that
might simplify a chunk of portage.py, too.

-- 
Batou: Hey, Major... You ever hear of "human rights"?
Kusanagi: I understand the concept, but I've never seen it in action.
  --Ghost in the Shell

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

      parent reply	other threads:[~2004-01-11 11:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-11  7:18 [gentoo-dev] GTK2 QT Theme Troy Dack
2004-01-11  7:57 ` Georgi Georgiev
2004-01-11  9:07   ` Troy Dack
2004-01-11  7:59 ` Spider
2004-01-11  8:32   ` Todd Berman
2004-01-11  9:58     ` Georgi Georgiev
2004-01-11 10:54   ` Troy Dack
2004-01-11 11:34   ` Drake Wyrm [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=20040111113452.GA19950@phaenix.haell.com \
    --to=wyrm@haell.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