From: "Chad M. Huneycutt" <chad.huneycutt@acm.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] stable and unstable branches.
Date: Wed, 24 Jul 2002 01:28:45 -0400 [thread overview]
Message-ID: <3D3E3B0D.4000804@acm.org> (raw)
In-Reply-To: 20020724063223.25c7e7d1.smiler@lanil.mine.nu
Christian Axelsson wrote:
> How about mask the "unstable" ebuilds in the stable distribution?
> That provides a simple solution for the Debian problem. If you want that
> new bleeding edge ebuild, just unmask it on your own risk. It will probably
> just be as stable as it is today.
> But to talk against myself on this:
KEYWORDS will let us do this alot more effectively. The way they work
is that an ebuild will have
KEYWORDS="unstable"
to indicate that an ebuild needs to be tested before it can be called
"stable". A user can list which keywords they will accept, so if you
accept "unstable" packages, then those will be available to you.
This is a rough description of how they will work. We still have some
details to work out, and I don't have the full picture yet, but expect
an announcement soon. We are also using this functionality to support
the alternative architectures.
Chad
next prev parent reply other threads:[~2002-07-24 5:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-23 20:06 [gentoo-dev] stable and unstable branches Stefano Peluchetti
2002-07-23 20:21 ` Karl Trygve Kalleberg
2002-07-23 20:58 ` Terje Kvernes
2002-07-23 21:31 ` Christian Bartl
2002-07-23 22:12 ` [gentoo-dev] stable and unstable branches. (auto-bug reports???) Stefano Peluchetti
[not found] ` <20020724001127.GC10394@athlon.dolly-llama.org>
2002-07-24 9:28 ` Stefano Peluchetti
2002-07-24 4:32 ` [gentoo-dev] stable and unstable branches Christian Axelsson
2002-07-24 5:28 ` Chad M. Huneycutt [this message]
2002-07-24 8:50 ` Alexander Gretencord
2002-07-24 15:32 ` Fredrik Jagenheim
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=3D3E3B0D.4000804@acm.org \
--to=chad.huneycutt@acm.org \
--cc=chadh@gentoo.org \
--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