1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
On Monday 21 June 2004 07:55, Travis Tilley wrote: |
5 |
> On Saturday 19 June 2004 11:21 am, foser wrote: |
6 |
> > -* means broken on all arches by definition. Sure it's a pretty good |
7 |
> > solution here for what you want to do, but it still is bending the |
8 |
> > rules. |
9 |
> |
10 |
> -* is the only way to add an ebuild for testing without forcing it on ~arch |
11 |
> users. i still have -* in keywords for the convenience of x86 users who |
12 |
> want to test and port x86 software to gcc 3.4 (and submit patches on |
13 |
> bugzilla) by simply adding "sys-devel/gcc -*" to package.keywords. |
14 |
|
15 |
Adding 'sys-devel/gcc -*' to package.keywords is *INCORRECT*. This is |
16 |
undocumented (and IMO broken) behaviour that cannot be relied upon. As foser |
17 |
said, "-* means broken on all arches by definition." Instead you should be |
18 |
encouraging the testers (and yourself) to copy the ebuild to your overlay and |
19 |
editing the KEYWORDS. |
20 |
|
21 |
Same goes for any other undocumented behaviour of portage. Don't try |
22 |
something, find it works and then use it - especially not in ebuilds. Doing |
23 |
so only slows down the progress of enhancements to portage as all whole heap |
24 |
of ugly crappy annoying backwards compatibility code (for something that was |
25 |
unintentional, mind you) needs to be maintained. |
26 |
|
27 |
If you don't know how to do it, ask. If it's not yet available, ask louder. |
28 |
|
29 |
Regards, |
30 |
Jason Stubbs |
31 |
-----BEGIN PGP SIGNATURE----- |
32 |
Version: GnuPG v1.2.4 (GNU/Linux) |
33 |
|
34 |
iQCVAwUBQNbOeFoikN4/5jfsAQL9uwP9GhYqQayr95AiW52uaU+aU5oRNV6Psq5l |
35 |
s5KQWP17Nc5Wr4CMKNX1bHDdFzgmTYT69e7ZcCJRE+qLWyO2MeOdxFES8+WLINqI |
36 |
yV180hi6zwI6/aDBjul23OF1yhfuul+0dQpNZsoguUdWJHKfH1431FKpYmtjvF3w |
37 |
sN1i1EfzrTw= |
38 |
=lS+u |
39 |
-----END PGP SIGNATURE----- |
40 |
|
41 |
-- |
42 |
gentoo-dev@g.o mailing list |