From: Thomas Anderson <gentoofan23@gentoo.org>
To: Greg KH <gregkh@gentoo.org>
Cc: Thomas Anderson <gentoofan23@gentoo.org>, gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in net-misc/bti: bti-007.ebuild ChangeLog metadata.xml Manifest
Date: Sun, 26 Oct 2008 18:29:13 -0400 [thread overview]
Message-ID: <20081026222913.GB12527@spoc> (raw)
In-Reply-To: <20081026215802.GA21085@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 1055 bytes --]
On Sun, Oct 26, 2008 at 02:58:02PM -0700, Greg KH wrote:
> On Sun, Oct 26, 2008 at 01:36:29PM -0400, Thomas Anderson wrote:
> > On Sun, Oct 26, 2008 at 05:22:26PM +0000, Greg Kroah-Hartman (gregkh) wrote:
> > > src_install() {
> > > doman bti.1
> > > dobin bti
> > > dodoc bti.example README RELEASE-NOTES
> > > }
> > You really should have some or all of these functions die on failure.
>
> Why would any of these fail if the src_compile succeeded?
"Succeeded" and "Not error out" are different. Src_compile could not
error out but still not produce the executables/produce an executable
with a different name. Either way you end up with a broken installation
of bti.
> And, for some reason I thought that the default was that if there was an
> error in them, they would "die" on their own. Is that not the case?
No, they don't die on their own. As far as I know, very few ebuild
functions do. Econf does, and epatch does as well. I'll look into
writing up a list of which functions die and which don't though, for
convenience.
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-10-26 22:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1Ku9Jq-0001dx-H1@stork.gentoo.org>
2008-10-26 17:36 ` [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in net-misc/bti: bti-007.ebuild ChangeLog metadata.xml Manifest Thomas Anderson
2008-10-26 21:58 ` Greg KH
2008-10-26 22:17 ` Thomas Sachau
2008-10-26 22:50 ` Greg KH
2008-10-26 22:29 ` Thomas Anderson [this message]
2008-10-26 22:51 ` Greg KH
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=20081026222913.GB12527@spoc \
--to=gentoofan23@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=gregkh@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