From: Jakub Moc <jakub@gentoo.org>
To: Jason Stubbs <gentoo-dev@lists.gentoo.org>
Subject: Re[2]: [gentoo-dev] making dodoc and dohtml die when they fail and stricter is on
Date: Mon, 26 Dec 2005 14:53:03 +0100 [thread overview]
Message-ID: <916873797.20051226145303@gentoo.org> (raw)
In-Reply-To: <200512262228.12764.jstubbs@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1338 bytes --]
26.12.2005, 14:28:12, Jason Stubbs wrote:
> On Monday 26 December 2005 20:01, 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.
> Sigh... None of these issues have made there way to dev-portage.
> --
> Jason Stubbs
Well, then assign Bug 116499 or Bug 116602 to yourself (qemu), there're
textrels in openoffice-bin, mozilla-firefox-bin (upstream, don't hold your
breath to get this fixed), acroread (cantfix really), this for sure will be
an issue for many games binaries, etc. While it's often upstream/cantfix, I
don't see much sense in making these QA checks fatal really.
--
Best regards,
Jakub Moc
mailto:jakub@gentoo.org
GPG signature: http://subkeys.pgp.net:11371/pks/lookup?op=get&search=0xCEBA3D9E
Primary key fingerprint: D2D7 933C 9BA1 C95B 2C95 B30F 8717 D5FD CEBA 3D9E
... still no signature ;)
[-- Attachment #2: Type: application/pgp-signature, Size: 183 bytes --]
next prev parent reply other threads:[~2005-12-26 13:56 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
2005-12-26 12:58 ` Danny van Dyk
2005-12-26 13:28 ` Jason Stubbs
2005-12-26 13:53 ` Jakub Moc [this message]
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=916873797.20051226145303@gentoo.org \
--to=jakub@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