public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Brad Laue <brad@brad-x.com>
To: "C. Brewer" <cbrewer@stealthaccess.net>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Is there a process for marking ebuilds stable?
Date: 15 Apr 2003 09:53:03 -0400	[thread overview]
Message-ID: <1050414783.2172.0.camel@localhost> (raw)
In-Reply-To: <20030414123954.46e3135b.cbrewer@stealthaccess.net>

On Mon, 2003-04-14 at 15:39, C. Brewer wrote:

> While I don't oppose your or anyones use of KDE, GNOME, or alsa, some things must be taken into consideration. I, for one, don't use a desktop environment, preferring a window-manager for my tasks, and I'm sure that I am not alone. Therefore you have negated that many testers with this sort of proposal (I for one run completely unstable). Secondly, while alsa may be the sound system of the future, it does not support all cards and some people are restricted to the kernel mods. Shorten your list of testers again. And since KDE and such require X, you leave out all of your CLI users, which will probably be your most critical old-schoolers and ex-UNIX peeps (gross stereotyping here). I think that it should stay that if it builds and runs with a reasonable amount of positive reports vs. bugs then it should go stable. I just wanted to point out that certain matters of selectiveness will negate your amount of testers, and probably work against your ends.
> 

Absolutely. One set of CFLAGS would have to logically exclude GNOME and
KDE extensions, to see whether the ebuild builds and merges without
these.

Brad


--
gentoo-dev@gentoo.org mailing list


  parent reply	other threads:[~2003-04-15 13:53 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-13 22:25 [gentoo-dev] Is there a process for marking ebuilds stable? Brad Laue
2003-04-13 23:00 ` Rainer Groesslinger
2003-04-13 23:07   ` Rainer Groesslinger
2003-04-13 23:07   ` Jon Portnoy
2003-04-14  9:31     ` Rainer Groesslinger
2003-04-14  7:32   ` Fredrik Jagenheim
2003-04-14  9:00     ` Michael Kohl
2003-04-14 11:04       ` Fredrik Jagenheim
2003-04-14 16:29         ` Mikael Andersson
2003-04-14 20:31           ` Alec Berryman
2003-04-14 21:48             ` Brad Laue
2003-04-14 21:58               ` Alec Berryman
2003-04-15 11:07                 ` Mikael Andersson
2003-04-14 22:03           ` Brad Laue
2003-04-14 15:07     ` Brad Laue
2003-04-14 19:39       ` C. Brewer
2003-04-15  6:21         ` Abhishek Amit
2003-04-15  9:09           ` Fredrik Jagenheim
2003-04-16  0:34           ` C. Brewer
2003-04-15 13:53         ` Brad Laue [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-04-15  2:08 Todd Wright
2003-04-15  2:30 ` Jon Portnoy
2003-04-15  5:41 ` Dylan Carlson

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=1050414783.2172.0.camel@localhost \
    --to=brad@brad-x.com \
    --cc=cbrewer@stealthaccess.net \
    --cc=gentoo-dev@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