Gentoo Archives: gentoo-dev

From: Duncan <1i5t5.duncan@×××.net>
To: gentoo-dev@l.g.o
Subject: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in net-analyzer/tcpreplay: ChangeLog tcpreplay-3.4.5_beta2.ebuild
Date: Sat, 30 Oct 2010 18:12:24
Message-Id: pan.2010.10.30.18.11.32@cox.net
In Reply to: Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in net-analyzer/tcpreplay: ChangeLog tcpreplay-3.4.5_beta2.ebuild by Jeroen Roovers
1 Jeroen Roovers posted on Sat, 30 Oct 2010 19:40:45 +0200 as excerpted:
2
3 > On Sat, 30 Oct 2010 09:44:42 +0400
4 > Peter Volkov <pva@g.o> wrote:
5 >
6 >> Also speaking about this specific package: I've maintained this package
7 >> quite long time and I'm following upstream mailing list and I've never
8 >> heard from upstream it's safe to push betas on all users.
9 >
10 > I didn't push it on all users. Maybe ~arch users, but they get to keep
11 > the pieces when they break their systems, if I recall correctly.
12
13 To some extent, yes.
14
15 However, Gentoo policy has always been that even ~arch is only upstream-
16 stable packages, the ~arch keyword denoting Gentoo package testing
17 (basically, the ebuild script and dependencies), /not/ upstream testing.
18 In with certain exceptions, in particular for packages where Gentoo itself
19 is upstream, if it's not a package that could at least in theory be Gentoo-
20 stable if no bugs appear during the 30-day standard stabilizing period,
21 it's not supposed to be ~arch keyworded either.
22
23 That's an important distinction to make.
24
25 --
26 Duncan - List replies preferred. No HTML msgs.
27 "Every nonfree program has a lord, a master --
28 and if you use the program, he is your master." Richard Stallman

Replies