1 |
Chris Gianelloni posted <1136575138.18383.77.camel@×××××××××××××××××.net>, |
2 |
excerpted below, on Fri, 06 Jan 2006 14:18:58 -0500: |
3 |
|
4 |
> Remember that the release trees would only be security fixes. No other |
5 |
> package updates should be happening. This would allow for companies to |
6 |
> actually certify their software against "Gentoo 2006.0", for example. |
7 |
|
8 |
Not an unreasonable proposal. I've a couple of comments, however. |
9 |
(Naturally. =8^) |
10 |
|
11 |
1) AFAIK, most such certification would require nailing down a bit |
12 |
further, including gcc version used to compile, and CFLAGS, among other |
13 |
things. Basically, what they'd then be certifying against would be the |
14 |
GRP releases. This could mean expanding them somewhat, altho it should be |
15 |
fine to build software unrelated to that being certified, and unrelated to |
16 |
the necessary boot environment, from source, without destroying the |
17 |
certification, and that limits the required GRP package count somewhat. |
18 |
|
19 |
2) I was going to say that without keyword support it might be difficult |
20 |
to nail down the distinction between those running current and those |
21 |
running stable, but I just realized it could/should be right there in the |
22 |
repository and/or profile information, as I'm sure that'll need to be |
23 |
reported in emerge info, once multi-repository gets full support. It |
24 |
/will/ be a bit of extra bug tracking for either devs or bug-wranglers or |
25 |
both, as devs not wanting the work of supporting "stale" packages will, |
26 |
I'm sure, still get bugs assigned that belong to the stable tree only. |
27 |
However, that should be minimal and manageable. |
28 |
|
29 |
-- |
30 |
Duncan - List replies preferred. No HTML msgs. |
31 |
"Every nonfree program has a lord, a master -- |
32 |
and if you use the program, he is your master." Richard Stallman in |
33 |
http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html |
34 |
|
35 |
|
36 |
-- |
37 |
gentoo-dev@g.o mailing list |