| 1 |
>> Currently there are quite a few ebuilds in the tree that execute dodoc or |
| 2 |
>> dohtml for files that do not exist. I think it would be nice to have |
| 3 |
>> ebuilds die if this is the case. To not break current ebuilds this would |
| 4 |
>> only happen with FEATURES="stricter". |
| 5 |
|
| 6 |
Sigh... There are already bugs flowing in for TEXTRELs/executable stacks |
| 7 |
checks implemented in recent portage versions. Some of these bugs are |
| 8 |
completely INVALID or CANTFIX - emulation stuff, binary-only ebuilds, etc. |
| 9 |
etc. What's the point of this breakage? Why are these QA checks fatal, |
| 10 |
causing ebuilds to bail out? How can you disable such checks per-ebuild |
| 11 |
(AFAIK - you can't) to not annoy users with QA notices and breakage one can |
| 12 |
do nothing about anyway? |
| 13 |
|
| 14 |
As Flameeyes pointed out, dodoc/dohtml is also used in eclasses. This can |
| 15 |
break many ebuilds. Users will report duplicate bugs because they will not |
| 16 |
realize that it's the eclass causing the failure, not the ebuild. Again, |
| 17 |
what's the point? How will it work with FEATURES="nodoc"? Why should an |
| 18 |
ebuild ever fail just because some doc file is missing or got renamed or |
| 19 |
whatever? |
| 20 |
|
| 21 |
|
| 22 |
-- |
| 23 |
Best regards, |
| 24 |
|
| 25 |
Jakub Moc |
| 26 |
mailto:jakub@g.o |
| 27 |
GPG signature: http://subkeys.pgp.net:11371/pks/lookup?op=get&search=0xCEBA3D9E |
| 28 |
Primary key fingerprint: D2D7 933C 9BA1 C95B 2C95 B30F 8717 D5FD CEBA 3D9E |
| 29 |
|
| 30 |
... still no signature ;) |
Archives