-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Jakub Moc schrieb:
|
|>>Currently there are quite a few ebuilds in the tree that execute dodoc or
|>>dohtml for files that do not exist. I think it would be nice to have
|>>ebuilds die if this is the case. To not break current ebuilds this would
|>>only happen with FEATURES="stricter".
|
|
| Sigh... There are already bugs flowing in for TEXTRELs/executable stacks
| checks implemented in recent portage versions. Some of these bugs are
| completely INVALID or CANTFIX - emulation stuff, binary-only ebuilds, etc.
| etc. What's the point of this breakage? Why are these QA checks fatal,
| causing ebuilds to bail out? How can you disable such checks per-ebuild
| (AFAIK - you can't) to not annoy users with QA notices and breakage
one can
| do nothing about anyway?
You can disable them. Have a look at dyn_install in ebuild.sh.
There are 2 categories of such QA violations:
* One category (qa_sucks_for_sure) currently only consists of ebuilds
~ that have run-paths pointing to a subdir of ${BUILDDIR}. Such bugs can
~ always be fixed (as it never affects binary packages) and thus this
~ category of bug lets the build process always die.
* The other category (qa_kinda_sucks) only causes the death of the build
~ process when the user has FEATURES="stricter" and the ebuild doesn't
~ have RESTRICT="stricter".
The obvious solution for unfixable (binary) packages is to set
RESTRICT="stricter" for them. On the other hand, some binary UPSTREAMs
are very kind and competent to handle such bugs if you tell them. AMD
for example, who will fix an "exectuable stack" problem in ACML after
the holidays.
Danny
- --
Danny van Dyk <[EMAIL PROTECTED]>
Gentoo/AMD64 Project, Gentoo Scientific Project
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFDr+j8aVNL8NrtU6IRAq0kAJ92IHWPU/WRRzj5F807yU+89bm87gCfbbBF
lkpmuU3EgpaFHfaCaiShQxI=
=drQA
-----END PGP SIGNATURE-----
--
gentoo-dev@gentoo.org mailing list
