| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
On 04/09/2013 08:12 PM, Donnie Berkholz wrote: |
| 5 |
> On 23:20 Mon 08 Apr , Ryan Hill wrote: |
| 6 |
>> Hrm. I just meant that package eclasses suck. I hate the fact |
| 7 |
>> that they effectively make stable moot. There is no such thing |
| 8 |
>> as a stable keyword for a package built by an eclass. It's like |
| 9 |
>> working without a net. When it's a core system package it's |
| 10 |
>> twice as bad. |
| 11 |
>> |
| 12 |
>> As far as these eclasses go, toolchain is the worst. Yes, it is |
| 13 |
>> fragile and complex. It's over a decade's worth of spaghetti |
| 14 |
>> code. It builds 12 years of gcc releases. It's hairy. |
| 15 |
>> Everything depends on everything else, and everything is based on |
| 16 |
>> assumptions and implications that may or may not still be |
| 17 |
>> relevant. Making "obviously" correct changes has often broken |
| 18 |
>> something somewhere else, time and again. I'm not telling you |
| 19 |
>> this for some kind of perverse bragging rights. It's not |
| 20 |
>> something to be proud of. I just want you to understand how easy |
| 21 |
>> it is to fuck things up. |
| 22 |
>> |
| 23 |
>> When it breaks, it breaks stable. I absolutely hate breaking |
| 24 |
>> stable. I lose sleep over it. |
| 25 |
> |
| 26 |
> You could probably deal with this through much more aggressive |
| 27 |
> bumping of eclass versions in concert with ebuild bumps, followed |
| 28 |
> by eclass freezes once their users go stable. |
| 29 |
> |
| 30 |
|
| 31 |
That makes it even worse IMO and introduces more confusion and |
| 32 |
complexity when writing/dealing with ebuilds. I am more thinking of |
| 33 |
something similar to autoconf. |
| 34 |
Once an ebuild goes stable it will be generated as a static ebuild |
| 35 |
based on the current state of the eclasses. That will introduce a few |
| 36 |
problems (such as how to handle global eclass scope), but I think they |
| 37 |
are solvable. |
| 38 |
Imo we could even ignore PMS here, since we would basically just dump |
| 39 |
all related eclass functions into the ebuild and drop the eclass inherit. |
| 40 |
We could write a tool to do and revert that and make it more readable etc. |
| 41 |
|
| 42 |
But this is just a thought, maybe I am wrong and it's even more |
| 43 |
complicated. |
| 44 |
-----BEGIN PGP SIGNATURE----- |
| 45 |
Version: GnuPG v2.0.19 (GNU/Linux) |
| 46 |
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ |
| 47 |
|
| 48 |
iQEcBAEBAgAGBQJRZVj4AAoJEFpvPKfnPDWzmb8H/03CUA/EYM5ZIiAGY9KqZZ9L |
| 49 |
/3wRtCG5ywfi7COq0xA08YK60Bj1pHiGgSaJvIu0e9SsVc/Vqv3g0Z0EBpUUA1DR |
| 50 |
3m8cqu7HpaG0N7MZ03jrRzzjo3bGmmkuvT2jG7d1YTUekfz1kpoUpe790F2Ps9IE |
| 51 |
fABT56pCZnE+Cnpa6G+pEbC7BBzSFsZC1A4XRRWiHaveWECDzC+ovexP08UV4BjS |
| 52 |
Pie5Od0oZNYUQtQyWE86ypS6Zd+LfguByblHkLj25s+1OgGvzkSc46pR3J5RKLFs |
| 53 |
gypJOe0IMWyn4/+YqGF+fQyPLBf4bhtUmzl+wF3ObkTUSF7uSU1n3ibvsH2BTAA= |
| 54 |
=bykX |
| 55 |
-----END PGP SIGNATURE----- |
Archives