public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Petteri Räty" <betelgeuse@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: gentoo-portage@dev.gentoo.org
Subject: [gentoo-dev] making dodoc and dohtml die when they fail and stricter is on
Date: Mon, 26 Dec 2005 01:32:05 +0200	[thread overview]
Message-ID: <43AF2BF5.4060905@gentoo.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1286 bytes --]

Moving this to gentoo-dev then.

-------- Original Message --------
Subject: Re: [gentoo-portage-dev] making dodoc and dohtml die when they
fail and stricter is on
Date: Sun, 25 Dec 2005 15:14:46 -0800
From: Brian Harring <ferringb@gentoo.org>
Reply-To: gentoo-portage-dev@lists.gentoo.org
To: gentoo-portage-dev@lists.gentoo.org
References: <43AF230C.5080904@gentoo.org>

On Mon, Dec 26, 2005 at 12:54:04AM +0200, Petteri Räty 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". This is what I currently do in my
> bashrc. Obviously when integreted to portage one can use helper
> functions like hasq which are not available in bashrc.
> 
> 
> if [[ "${FEATURES/stricter}" != "${FEATURES}" ]]; then
> 
> _makefail() {
> 	bin="/usr/lib/portage/bin/${1}"
> 	shift 1
> 	"${bin}" "${@}" || die "${bin} ${@} failed"
> }
> 
> dodoc() {	_makefail ${FUNCNAME} "${@}"; }
> dohtml() {	_makefail ${FUNCNAME} "${@}"; }
Seems like more of a -dev discussion imo, since they're the ones
affected by it (for us it's just an api change).
~harring



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]

             reply	other threads:[~2005-12-25 23:34 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-25 23:32 Petteri Räty [this message]
2005-12-26  0:13 ` [gentoo-dev] making dodoc and dohtml die when they fail and stricter is on 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       ` 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=43AF2BF5.4060905@gentoo.org \
    --to=betelgeuse@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=gentoo-portage@dev.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