From: Ed W <lists@wildgooses.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [Summary] tentative x86 arch team glep
Date: Tue, 06 Sep 2005 18:03:37 +0100 [thread overview]
Message-ID: <431DCBE9.4090907@wildgooses.com> (raw)
In-Reply-To: <200509061903.39000.chriswhite@gentoo.org>
As an "outsider" reading that summary the message *I* read is that there
is some strain over fitting the development model into "stable", "~",
and "package.mask". I think I see people basically saying that they
have differing views over what qualifies for each level?
Perhaps part of the solution is to review the current list of "levels"
of stability? Debian for example use several levels with something
like: stable, unstable, testing, development (or whatever they are
called). Perhaps something more like that would be useful for gentoo?
I do know as a user it can be quite frustrating trying to find the
ebuild for a package and having to dig around bugs.gentoo, and some
other website, then patch up a dodgy ebuild found on some website, etc,
etc. Perhaps it would be more useful to have "development quality"
ebuilds straight from portage (labelled as dangerous and unstable of
course) and then I could more easily file back patches to fix problems
that I find, and development would be more centralised...?
Also, as someone who has submitted a few patches and some ebuilds and
then seen nothing happen to them and my offers to act as maintainer have
gone unresponded I also wonder if there is some way to make better use
of casual contributors like me? (I'm not bitter, it's just that I feel I
could contribute more, but don't know how to?)
Good luck. I'm a big gentoo fan. I hope this extends gentoos lead even
further!
All the best
Ed W
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-09-06 17:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-06 10:03 [gentoo-dev] [Summary] tentative x86 arch team glep Chris White
2005-09-06 12:35 ` Mike Doty
2005-09-06 17:03 ` Ed W [this message]
2005-09-06 17:21 ` Ciaran McCreesh
2005-09-06 20:07 ` Alec Joseph Warner
2005-09-11 23:53 ` Ed W
2005-09-12 0:03 ` Ciaran McCreesh
2005-09-12 17:04 ` Ed W
2005-09-12 17:19 ` Michael Kohl
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=431DCBE9.4090907@wildgooses.com \
--to=lists@wildgooses.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