| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA256 |
| 3 |
|
| 4 |
On 27/08/13 05:59 AM, Ulrich Mueller wrote: |
| 5 |
> In a nutshell: The default src_install() implementation in EAPIs 4 |
| 6 |
> and 5 is flawed because it doesn't account for the DOCS variable |
| 7 |
> being defined but empty. It ends up calling dodoc without any |
| 8 |
> arguments in this case. This will work in Portage (with a QA |
| 9 |
> warning), but the stricter implementation in Paludis will error |
| 10 |
> out. |
| 11 |
> |
| 12 |
> 2. There is consensus that default src_install should be fixed in |
| 13 |
> the next EAPI. The question is if we should retroactively change |
| 14 |
> the specification [3]. |
| 15 |
|
| 16 |
(Replying to original list -- are we supposed to move these |
| 17 |
discussions to -dev@ ??) |
| 18 |
|
| 19 |
It's unfortunate that this bug is there (DOCS must always have a value |
| 20 |
in the default src_install, whether it be set by the default phase or |
| 21 |
in the ebuild), but I don't think we can just retroactively fix |
| 22 |
EAPI4/5 to do it without consensus from all of the PM implementation |
| 23 |
upstreams. Inviting them all to the council meeting to seek their |
| 24 |
approval is always a possibility, of course. |
| 25 |
|
| 26 |
It would probably be best to just enforce workarounds in eclasses and |
| 27 |
remove the empty/null assignments in ebuilds, and make sure the spec |
| 28 |
(and therefore PMs) are fixed to allow empty DOCS in EAPI6 and above. |
| 29 |
|
| 30 |
|
| 31 |
|
| 32 |
-----BEGIN PGP SIGNATURE----- |
| 33 |
Version: GnuPG v2.0.20 (GNU/Linux) |
| 34 |
|
| 35 |
iF4EAREIAAYFAlIctJAACgkQ2ugaI38ACPBrKwD9HKGj9mZLrHmK9OlBkwngp20M |
| 36 |
l2CVE+X5l9bFCK4g0KUA/3FT6+h0sb3UrW+eK+/mvTBabLIbgIrFV+rgjfZhjprc |
| 37 |
=c7bt |
| 38 |
-----END PGP SIGNATURE----- |
Archives