public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@gentoo.org>
To: Thomas Anderson <gentoofan23@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org, gregkh@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 14:58:02 -0700	[thread overview]
Message-ID: <20081026215802.GA21085@kroah.com> (raw)
In-Reply-To: <20081026173629.GA4330@spoc>

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:
> > # Copyright 1999-2008 Gentoo Foundation
> > # Distributed under the terms of the GNU General Public License v2
> > # $Header: /var/cvsroot/gentoo-x86/net-misc/bti/bti-007.ebuild,v 1.1 2008/10/26 17:22:26 gregkh Exp $
> > 
> > RDEPEND="${DEPEND}"
> > 
> > src_compile() {
> > 	emake || die "emake failed"
> > }
> This is the default src_compile.

Ah, thanks, I should just drop this then.

> > 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?

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?

> Since that's all the ebuild installs, the package is completely
> nonfunctional if bti is not installed(I'd die on all three but you don't
> have to die on the last one).

Might as well be consistent :)

thanks for the review,

greg k-h



  reply	other threads:[~2008-10-26 22:00 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 [this message]
2008-10-26 22:17     ` Thomas Sachau
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=20081026215802.GA21085@kroah.com \
    --to=gregkh@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=gentoofan23@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