From: Ian Leitch <port001@gentoo.org>
To: Lisa Seelye <lisa@gentoo.org>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Three teir portage: stable, prestable, unstable?
Date: Mon, 06 Oct 2003 23:08:06 +0100 [thread overview]
Message-ID: <1065478086.4139.38.camel@Interimo.Intern.LAN> (raw)
In-Reply-To: <1065473505.28246.7.camel@lisa.thedoh.com>
On Mon, 2003-10-06 at 21:51, Lisa Seelye wrote:
> On Mon, 2003-10-06 at 17:47, Ian Leitch wrote:
> > Hi everyone,
> >
> > I'm sure this HAS to have been discussed before, and if it has, it was
> > before my time. I'd like to hear peoples opinions and what the
> > conclusion was from earlier discussions.
> >
> > Just to make everything clear, I will outline exactly what I have in
> > mind.
> >
> > In my view, the portage tree would benefit from having the following:
>
> How? Why does this warrant a radical change to the system?
As I'm sure all devs know, ~arch is used for other things than just
testing ebuilds.
"The purpose of ~arch is for testing new packages added to Portage. This
is not the equivalent of "testing" of "unstable" in other
distributions." - Development Policy
Making these changes would sort out this little problem/mess whatever
you want to call it. I also think the extra unstable branch would take
some weight off package.mask, which could then be reserved for the need
to mask a package for temporary licensing issues etc.. without removing
it from portage.
Stable would also gradulay become more stable. We can't match Debian for
stability but we could have the best of both worlds: up-to-date,
reasonably stable software. This must be pretty attractive to those
using Gentoo on the server and more importantly, those thinking about
it.
Regards,
Ian.
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-10-06 21:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-06 21:47 [gentoo-dev] Three teir portage: stable, prestable, unstable? Ian Leitch
2003-10-06 20:51 ` Lisa Seelye
2003-10-06 22:08 ` Ian Leitch [this message]
2003-10-06 22:08 ` foser
2003-10-07 9:46 ` Paul de Vrieze
2003-10-07 12:07 ` foser
2003-10-07 13:04 ` Paul de Vrieze
2003-10-07 14:30 ` foser
2003-10-07 18:49 ` Ian Leitch
2003-10-07 18:10 ` brett holcomb
2003-10-07 18:27 ` Paul de Vrieze
2003-10-07 21:57 ` Jason Stubbs
2003-10-07 21:41 ` foser
2003-10-06 21:00 ` Stuart Herbert
2003-10-06 21:22 ` Mike Frysinger
2003-10-06 21:56 ` Sven Blumenstein
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=1065478086.4139.38.camel@Interimo.Intern.LAN \
--to=port001@gentoo.org \
--cc=gentoo-dev@gentoo.org \
--cc=lisa@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