| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Jakub Moc schrieb: |
| 5 |
| |
| 6 |
|>>Currently there are quite a few ebuilds in the tree that execute dodoc or |
| 7 |
|>>dohtml for files that do not exist. I think it would be nice to have |
| 8 |
|>>ebuilds die if this is the case. To not break current ebuilds this would |
| 9 |
|>>only happen with FEATURES="stricter". |
| 10 |
| |
| 11 |
| |
| 12 |
| Sigh... There are already bugs flowing in for TEXTRELs/executable stacks |
| 13 |
| checks implemented in recent portage versions. Some of these bugs are |
| 14 |
| completely INVALID or CANTFIX - emulation stuff, binary-only ebuilds, etc. |
| 15 |
| etc. What's the point of this breakage? Why are these QA checks fatal, |
| 16 |
| causing ebuilds to bail out? How can you disable such checks per-ebuild |
| 17 |
| (AFAIK - you can't) to not annoy users with QA notices and breakage |
| 18 |
one can |
| 19 |
| do nothing about anyway? |
| 20 |
You can disable them. Have a look at dyn_install in ebuild.sh. |
| 21 |
There are 2 categories of such QA violations: |
| 22 |
|
| 23 |
* One category (qa_sucks_for_sure) currently only consists of ebuilds |
| 24 |
~ that have run-paths pointing to a subdir of ${BUILDDIR}. Such bugs can |
| 25 |
~ always be fixed (as it never affects binary packages) and thus this |
| 26 |
~ category of bug lets the build process always die. |
| 27 |
|
| 28 |
* The other category (qa_kinda_sucks) only causes the death of the build |
| 29 |
~ process when the user has FEATURES="stricter" and the ebuild doesn't |
| 30 |
~ have RESTRICT="stricter". |
| 31 |
|
| 32 |
The obvious solution for unfixable (binary) packages is to set |
| 33 |
RESTRICT="stricter" for them. On the other hand, some binary UPSTREAMs |
| 34 |
are very kind and competent to handle such bugs if you tell them. AMD |
| 35 |
for example, who will fix an "exectuable stack" problem in ACML after |
| 36 |
the holidays. |
| 37 |
|
| 38 |
Danny |
| 39 |
- -- |
| 40 |
Danny van Dyk <kugelfang@g.o> |
| 41 |
Gentoo/AMD64 Project, Gentoo Scientific Project |
| 42 |
-----BEGIN PGP SIGNATURE----- |
| 43 |
Version: GnuPG v1.4.1 (GNU/Linux) |
| 44 |
|
| 45 |
iD8DBQFDr+j8aVNL8NrtU6IRAq0kAJ92IHWPU/WRRzj5F807yU+89bm87gCfbbBF |
| 46 |
lkpmuU3EgpaFHfaCaiShQxI= |
| 47 |
=drQA |
| 48 |
-----END PGP SIGNATURE----- |
| 49 |
-- |
| 50 |
gentoo-dev@g.o mailing list |
Archives