From: "Petteri Räty" <betelgeuse@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] making dodoc and dohtml die when they fail and stricter is on
Date: Mon, 26 Dec 2005 14:53:07 +0200 [thread overview]
Message-ID: <43AFE7B3.8010602@gentoo.org> (raw)
In-Reply-To: <1566320872.20051226120137@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1779 bytes --]
Jakub Moc wrote:
>
>>>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?
>
> As Flameeyes pointed out, dodoc/dohtml is also used in eclasses. This can
> break many ebuilds. Users will report duplicate bugs because they will not
> realize that it's the eclass causing the failure, not the ebuild. Again,
> what's the point? How will it work with FEATURES="nodoc"? Why should an
> ebuild ever fail just because some doc file is missing or got renamed or
> whatever?
>
>
echo "dodoc: ${x} does not exist" 1>&2
This should not be showed to users then because we know this to happen
and do not want to do anything about it. Also try to remember that not
every package is done following the GNU conventions (Java). It can
happen that the doc files are for example renamed and dieing will help
catch this. dodoc/dohtml dieing will not have any affect on
FEATURES="nodoc".
How about making it possible to tell dodoc/dohtml not to die as an
argument/variable/whatever? We could also have new diedodoc functions,
but it would be nice to keep this as simple as possible.
Regards,
Petteri
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]
next prev parent reply other threads:[~2005-12-26 12:57 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-25 23:32 [gentoo-dev] making dodoc and dohtml die when they fail and stricter is on Petteri Räty
2005-12-26 0:13 ` Jason Stubbs
2005-12-26 11:01 ` Jakub Moc
2005-12-26 12:53 ` Petteri Räty [this message]
2005-12-26 12:58 ` Danny van Dyk
2005-12-26 13:28 ` Jason Stubbs
2005-12-26 13:53 ` Re[2]: " Jakub Moc
2005-12-26 1:26 ` Diego 'Flameeyes' Pettenò
2005-12-26 2:28 ` Chris White
2005-12-26 12:04 ` Diego 'Flameeyes' Pettenò
2005-12-26 12:44 ` Petteri Räty
2005-12-26 12:59 ` Simon Stelling
2005-12-26 14:14 ` Diego 'Flameeyes' Pettenò
2005-12-26 14:32 ` Dan Meltzer
2005-12-26 14:44 ` Dan Meltzer
2005-12-27 19:41 ` [gentoo-dev] Putting qa warnings to a text file instead of showing them to the world Petteri Räty
2005-12-27 19:58 ` Mike Frysinger
2005-12-27 20:02 ` Lares Moreau
2005-12-27 20:10 ` Petteri Räty
2005-12-27 20:22 ` Lares Moreau
2005-12-28 1:34 ` Kalin KOZHUHAROV
2005-12-28 1:53 ` Lares Moreau
2005-12-28 2:03 ` Kalin KOZHUHAROV
2005-12-28 3:21 ` Ryan Tandy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43AFE7B3.8010602@gentoo.org \
--to=betelgeuse@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox