| 1 |
Brad Laue wrote:[Tue Nov 18 2003, 11:02:43AM EST] |
| 2 |
> As vapier stated, the ebuild was removed because it is old. It is the |
| 3 |
> responsibility of each architecture maintainer to keep the mozilla |
| 4 |
> versions up to date. |
| 5 |
|
| 6 |
This comes down to a scalability issue. There's ~3 people working on |
| 7 |
alpha, and ~2 working on ia64. The current KEYWORDS system has definite |
| 8 |
scalability problems becuase it expects each arch team to keep up with |
| 9 |
all the ebuilds in the tree. Until the system changes, developers might |
| 10 |
need to keep ebuilds around longer than they would otherwise like. |
| 11 |
|
| 12 |
> I have asked repeatedly that people do this, as I do not have IA64, |
| 13 |
> SPARC, AMD64 or PowerPC systems available to me on which I can build and |
| 14 |
> test Mozilla out. |
| 15 |
|
| 16 |
It's really helpful that you do that. Thanks. |
| 17 |
|
| 18 |
> The userbase can help their respective architectures out by stating that |
| 19 |
> a specific version of Mozilla is serviceable on theirs, and ask to have |
| 20 |
> it marked 'arch' on their particular CPU type. |
| 21 |
|
| 22 |
Yes, that's a huge help. It allows us to prioritize ebuilds that users |
| 23 |
are actually using.. |
| 24 |
|
| 25 |
Aron |
| 26 |
|
| 27 |
-- |
| 28 |
Aron Griffis |
| 29 |
Gentoo Linux Developer |
| 30 |
Key fingerprint = E3B6 8734 C2D6 B5E5 AE76 FB3A 26B1 C5E3 2010 4EB0 |
Archives