From: Thomas Sachau <tommy@gentoo.org>
To: gregkh@gentoo.org
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in net-misc/bti: bti-007.ebuild ChangeLog metadata.xml Manifest
Date: Sun, 26 Oct 2008 23:17:14 +0100 [thread overview]
Message-ID: <4904EC6A.5070303@gentoo.org> (raw)
In-Reply-To: <20081026215802.GA21085@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 780 bytes --]
Greg KH schrieb:
>>> 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?
What happens, if upstream changes the name of the binary on version bump or changes the compile
output location?
>
> 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?
Sadly not. Some functions do die (like epatch or econf), others do not (like emake, dobin,
doman....). If i remember correctly, those that are external functions do die, the others do not.
--
Thomas Sachau
Gentoo Linux Developer
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 315 bytes --]
next prev parent reply other threads:[~2008-10-26 22:17 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 [this message]
2008-10-26 22:50 ` Greg KH
2008-10-26 22:29 ` Thomas Anderson
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=4904EC6A.5070303@gentoo.org \
--to=tommy@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