| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA256 |
| 3 |
|
| 4 |
On 10/04/13 11:02 AM, Tom Wijsman wrote: |
| 5 |
> On Wed, 10 Apr 2013 16:20:20 +0200 hasufell <hasufell@g.o> |
| 6 |
> wrote: |
| 7 |
> |
| 8 |
>> That environment file saves the whole environment including user |
| 9 |
>> settings. How does that fit the idea I just posted here? It does |
| 10 |
>> not. |
| 11 |
> |
| 12 |
> "It will be generated as a static ebuild based on the current state |
| 13 |
> of the eclasses", that's a part of what the environment file does. |
| 14 |
> |
| 15 |
|
| 16 |
The environment includes per-system-specific results, though, not just |
| 17 |
the result of the ebuild plus insertion of all eclasses listed in the |
| 18 |
inherit line(s), no? Also, we probably don't actually want ALL of the |
| 19 |
eclasses to be inlined, just toolchain. |
| 20 |
|
| 21 |
|
| 22 |
|
| 23 |
> |
| 24 |
> When you generate ebuilds out of eclasses, you are effectively |
| 25 |
> generating versions of the current eclass as well. And when |
| 26 |
> someone experiences a problem that is caused due to an eclass, it |
| 27 |
> will be much easier to deal with it if we had the eclass in its |
| 28 |
> original form rather than its generated ebuild form. Actual |
| 29 |
> versions lead to less confusion. |
| 30 |
> |
| 31 |
|
| 32 |
That is a double-edged sword, though. What happens if the fix you |
| 33 |
need for a more current gcc breaks older ones? Or likewise, the fix |
| 34 |
you need for an older gcc for a small edge-case bug doesn't apply to |
| 35 |
newer versions? |
| 36 |
|
| 37 |
I believe what hasufell is suggesting is essentially that we could, |
| 38 |
via inlining a snapshot of toolchain.eclass (et al) into stable |
| 39 |
ebuilds, implement elcass versioning without having multiple versions |
| 40 |
of the actual toolchain.eclass file. So we get the advantage of |
| 41 |
versioning without the nastiness of having to handle and organize |
| 42 |
who-knows-how-many toolchain-###.eclass files, with the only drawback |
| 43 |
being that changes required to bugfix stable ebuilds would possibly |
| 44 |
need to be forward-ported to the eclass if it applies. |
| 45 |
|
| 46 |
|
| 47 |
|
| 48 |
-----BEGIN PGP SIGNATURE----- |
| 49 |
Version: GnuPG v2.0.19 (GNU/Linux) |
| 50 |
|
| 51 |
iF4EAREIAAYFAlFllsQACgkQ2ugaI38ACPCnUQD9GMBCOetzttYQ7T5iHJU0qjjd |
| 52 |
ltNJeCII4XNkdszmkh4BAK0Erb4+P2rdmtzDQXqLuJMTVE3hBQSYaxfD0jcJDng/ |
| 53 |
=VqXp |
| 54 |
-----END PGP SIGNATURE----- |
Archives