From: Andrew Muraco <tuxp3@leetworks.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] first council meeting
Date: Mon, 26 Sep 2005 00:01:57 -0400 [thread overview]
Message-ID: <433772B5.9050909@leetworks.com> (raw)
In-Reply-To: <20050918124024.GB7222@pluto.atHome>
In response to all replies Thus far,
I as a User,
I expect that arch works (no matter what) - no arguments there
I assume that ~arch will work 95% of the time.
I never ever touch anything in p.mask.
Now, where do we put packages that could work for most users, but they
might not work for the other 49% of users?
p.mask seems to prevent that 49% of users from trying it, and reporting
those bugs, but on the other hand ~arch means that 49% of users using
~arch will have problem x,y, or z.
Now understand, this is the viewpoint of myself, and I have used a full
~arch system for a while, and i didn't ever run into anything more then
the occasional package with a new config, or config update that i didnt
do properly. (lazy-ness)
things to consider
1) would ?arch become the old ~arch, if it was implemented?
2) would people actually try to run a full ?arch system?
3) #2, would it be possible without breakage?
I personally like the idea of the UNSTABLE="" because to me, it changes
nothing, but allows the AT and PM to communicate, on a per-ebuild basis.
(comments welcome)
just some thoughts,
Andrew
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-09-26 3:55 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-15 20:51 [gentoo-dev] first council meeting Aron Griffis
2005-09-15 21:25 ` Olivier Crete
2005-09-15 21:57 ` Chris Gianelloni
2005-09-15 22:20 ` Mike Frysinger
2005-09-16 17:42 ` Paul de Vrieze
2005-09-16 18:14 ` Martin Schlemmer
2005-09-16 18:18 ` Brian Harring
2005-09-16 18:19 ` Simon Stelling
2005-09-16 18:38 ` Ciaran McCreesh
2005-09-16 18:48 ` Paul de Vrieze
2005-09-16 19:00 ` Daniel Ostrow
2005-09-17 9:28 ` Kevin F. Quinn
2005-09-17 9:34 ` Brian Harring
2005-09-17 12:02 ` Kevin F. Quinn
2005-09-17 20:17 ` Mike Frysinger
2005-09-17 21:59 ` Alec Warner
2005-09-17 22:45 ` Mike Frysinger
2005-09-18 6:46 ` Wernfried Haas
2005-09-18 6:51 ` Wernfried Haas
2005-09-18 12:32 ` Ciaran McCreesh
2005-09-18 13:01 ` Wernfried Haas
2005-09-18 14:05 ` Alec Warner
2005-09-19 1:58 ` Philip Webb
2005-09-18 15:38 ` Ciaran McCreesh
2005-09-18 12:40 ` Matti Bickel
2005-09-26 4:01 ` Andrew Muraco [this message]
2005-09-26 4:15 ` Mike Frysinger
2005-09-28 2:53 ` Marius Mauch
2005-09-16 19:02 ` Ciaran McCreesh
2005-09-16 19:12 ` Simon Stelling
2005-09-16 19:34 ` Ciaran McCreesh
2005-09-16 20:46 ` Simon Stelling
2005-09-16 19:15 ` Mike Frysinger
2005-09-16 19:34 ` Ciaran McCreesh
2005-09-16 20:11 ` Paul de Vrieze
2005-09-16 20:21 ` Aron Griffis
2005-09-16 20:25 ` Daniel Ostrow
2005-09-16 20:43 ` Mike Frysinger
2005-09-16 21:50 ` Mike Frysinger
2005-09-16 22:00 ` Kito
2005-09-16 22:23 ` Maurice van der Pot
2005-09-16 22:45 ` Carsten Lohrke
2005-09-16 23:14 ` Mike Frysinger
2005-09-16 20:37 ` Olivier Crete
2005-09-16 20:17 ` Carsten Lohrke
2005-09-16 20:38 ` Ciaran McCreesh
2005-09-16 21:23 ` Carsten Lohrke
2005-09-16 21:34 ` Ciaran McCreesh
2005-09-16 21:41 ` Patrick Lauer
2005-09-16 21:46 ` Ciaran McCreesh
2005-09-16 22:43 ` Carsten Lohrke
2005-09-16 23:00 ` Ciaran McCreesh
2005-09-16 23:19 ` Carsten Lohrke
2005-09-16 20:33 ` Mike Frysinger
2005-09-16 20:44 ` Ciaran McCreesh
2005-09-16 20:59 ` Mike Frysinger
2005-09-16 21:10 ` Ciaran McCreesh
2005-09-16 21:20 ` Simon Stelling
2005-09-16 21:26 ` Ciaran McCreesh
2005-09-16 21:51 ` Mike Frysinger
2005-09-19 9:32 ` Paul de Vrieze
2005-09-16 22:48 ` Carsten Lohrke
2005-09-16 21:57 ` Martin Schlemmer
2005-09-16 22:17 ` Mike Frysinger
2005-09-24 13:44 ` [gentoo-dev] " Duncan
2005-09-16 22:51 ` [gentoo-dev] " Carsten Lohrke
2005-09-16 20:16 ` Aron Griffis
2005-09-17 6:39 ` Elfyn McBratney
2005-09-15 23:47 ` Jason Stubbs
2005-09-24 13:21 ` [gentoo-dev] " 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=433772B5.9050909@leetworks.com \
--to=tuxp3@leetworks.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