1 |
On Wed, 2004-06-23 at 14:39, foser wrote: |
2 |
> On Wed, 2004-06-23 at 15:08 +0000, Ferris McCormick wrote: |
3 |
> > > Read my other reply to where you say the same thing : it's duplication |
4 |
> > > of info. Duplication is bad. |
5 |
> > > |
6 |
> > > - foser |
7 |
> > > |
8 |
> > I don't think it's just duplication. There have been so many of these, I |
9 |
> > am not sure which one to attach this thought to, so I picked this one |
10 |
> > because it is short. And, if I understand your point, this speaks to it. |
11 |
> > |
12 |
> > I am arch(sparc), so for definiteness, I use sparc as a placeholder for |
13 |
> > any architecture. |
14 |
> > |
15 |
> > 1. In one instance, if I, as sparc, mark something as KEYWORDS=sparc, it |
16 |
> > means essentially one thing: In my best judgment this package is |
17 |
> > stable for use on sparc. It doesn't say anything about other |
18 |
> > architectures (except as evidence of goodness). |
19 |
> |
20 |
> You are not the package maintainer, you should not mark it stable before |
21 |
> that happens. So your arch going stable has no wider significance. |
22 |
|
23 |
A package maintainer doubles as arch maintainer for that package and |
24 |
shouldn't be forced to hold it back from stable on an arch it is stable |
25 |
on just because it isn't stable on every arch. |
26 |
|
27 |
That kind of freedom from essentially pointless inter-arch dependencies |
28 |
is one of the things I enjoy about Gentoo. |
29 |
-- |
30 |
Donnie Berkholz |
31 |
Gentoo Linux |