| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Dne 27.1.2011 18:16, Ciaran McCreesh napsal(a): |
| 5 |
> On Thu, 27 Jan 2011 18:07:30 +0100 |
| 6 |
> Tomáa Chvátal <scarabeus@g.o> wrote: |
| 7 |
>> Ok bad example on the posix-sh file. But anyway even you can check |
| 8 |
>> what stuff the thing does and decide upon it. Anyway even tho you |
| 9 |
>> nitpick on something you don't need to. |
| 10 |
>> There is at minimal the binary files example where you just place them |
| 11 |
>> somewhere into $DATADIR, and oh cp a |
| 12 |
>> $DESTDIR/$DATADIR/$PN/mybinaryfile (image/pdfstuff/whatever) is so |
| 13 |
>> unportable... So we already know that it might have use now lets |
| 14 |
>> focus onto finding out if there is enough consumers it is worth to |
| 15 |
>> provide something easier than keywording it all archs and then |
| 16 |
>> stabling them, shall we? |
| 17 |
> |
| 18 |
> A long long time ago, Gentoo had a developer who keyworded lots of |
| 19 |
> things that he thought were "probably portable" ~sparc. Needless to say, |
| 20 |
> he was often wrong, despite being considerably more experienced on |
| 21 |
> portability issues than most package maintainers. Clearing that mess up |
| 22 |
> took several years of hard work... |
| 23 |
> |
| 24 |
> What you're proposing will make things harder for arch teams, not |
| 25 |
> easier. It will also make things harder for package maintainers when |
| 26 |
> they suddenly have to switch their packages from being noarch to being |
| 27 |
> most but not all archs. It will also make things harder for users, who |
| 28 |
> accept ~noarch for a package which then gets changed to use ~archs |
| 29 |
> instead, resulting in a downgrade. |
| 30 |
> |
| 31 |
Ok example implementation and solution: |
| 32 |
If ebuild contains ~noarch in KEYWORDS it is not permitted to contain |
| 33 |
anything else. |
| 34 |
~noarch located in KEYWORDS is translated as full testing keywords for |
| 35 |
every known architecture by package manager. If depgraph is to be found |
| 36 |
broken for such architecture it is shadowed (or treated as without |
| 37 |
keywords, whatever we find to like in our implementation in package |
| 38 |
manager) and not permitted to be emerged on said architecture. |
| 39 |
If noarch is to be found in KEYWORDS the package is treated the same way |
| 40 |
as ~noarch expect that it pose and use under stable tree. If noarch |
| 41 |
package can satisfy its depgraph in ~ but not in stable tree it is |
| 42 |
posing as testing for said architecture. |
| 43 |
|
| 44 |
Adding ebuilds with noarch keyword must be preceded with: |
| 45 |
All ebuilds seeking to have this feature implemented must be discussed |
| 46 |
on #gentoo-dev mailing list and proven not having portability issues. |
| 47 |
-----BEGIN PGP SIGNATURE----- |
| 48 |
Version: GnuPG v2.0.17 (GNU/Linux) |
| 49 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ |
| 50 |
|
| 51 |
iEYEARECAAYFAk1BspkACgkQHB6c3gNBRYezWACdGy16k/2XdOQAnltswSUufYb1 |
| 52 |
uF4AoL9zv474aLoHqhJgAxJ1vopkeHaL |
| 53 |
=bVNH |
| 54 |
-----END PGP SIGNATURE----- |
Archives