| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
On Thu, 10 Mar 2005, Alin Nastac wrote: |
| 5 |
|
| 6 |
> I'm only annoyed by the bad attitude of some devs who will get involved only |
| 7 |
> what suits them, forgetting that if they would not help, no one will. Btw, |
| 8 |
> what is the sense of ~arch if not "testing"? No gentooer expects from a ~arch |
| 9 |
> ebuild to be stable, so the sky would not fall if you made a mistake and |
| 10 |
> release it under this keyword. When I hear "I cannot mark foo library as |
| 11 |
> ~arch because I don't know how to test it" smells like excuse to me. |
| 12 |
|
| 13 |
When a package is marked ~arch, it's also supposed to work (or have worked |
| 14 |
in a previous version). |
| 15 |
|
| 16 |
Also it may help to look at things from an arch maintainers points of |
| 17 |
view. We are responsible for essentially maintaining almost every package |
| 18 |
in the tree for our architecture. When we ask for testing criteria with |
| 19 |
regards to a request for keywording, it's because it makes both of our |
| 20 |
lives easier and helps to improve QA as we arch maintainers don't know a |
| 21 |
lot about your application and don't have the time to get to know it like |
| 22 |
you do. This is especially helpful when dealing with libraries. |
| 23 |
|
| 24 |
Cheers, |
| 25 |
- -- |
| 26 |
Jason Wever |
| 27 |
Gentoo/Sparc Co-Team Lead |
| 28 |
-----BEGIN PGP SIGNATURE----- |
| 29 |
Version: GnuPG v1.2.6 (GNU/Linux) |
| 30 |
|
| 31 |
iD8DBQFCL4iCdKvgdVioq28RAhqxAKC2MDFXkkHaX97d2FyX22H4V7Q0ZACgg9Fm |
| 32 |
SCaOh/OJ0fjnnDZVZRutG9A= |
| 33 |
=snEB |
| 34 |
-----END PGP SIGNATURE----- |
| 35 |
-- |
| 36 |
gentoo-dev@g.o mailing list |
Archives