Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-dev
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-dev@g.o
From: Peter Volkov <pva@g.o>
Subject: Re: Usage of econf with an additional || die
Date: Tue, 30 Sep 2008 10:55:58 +0400
В Вск, 28/09/2008 в 20:24 +0200, Thomas Sachau пишет:
> I see many ebuild that still use "econf || die", also econf should die by itself. Are there any
> specific reasons for this? Some cases where econf does not die also it fails? Or some other reason
> for this?

This || die is redundant. Personally I remove it in every package I
touch and I suggest others do the same. People use our tree to learn how
to write ebuilds, so it's good idea to have consistent syntax in our
ebuilds...

-- 
Peter.



Replies:
Re: Usage of econf with an additional || die
-- Zac Medico
Re: Usage of econf with an additional || die
-- Ben de Groot
References:
Re: Default src_install for EAPI-2 or following EAPI
-- Ulrich Mueller
Re: Re: Default src_install for EAPI-2 or following EAPI
-- Thomas Sachau
Re: Re: Default src_install for EAPI-2 or following EAPI
-- Bo Ørsted Andresen
Re: Re: Default src_install for EAPI-2 or following EAPI
-- Nirbheek Chauhan
Re: Re: Default src_install for EAPI-2 or following EAPI
-- Thomas Sachau
Usage of econf with an additional || die
-- Thomas Sachau
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: Usage of econf with an additional || die
Next by thread:
Re: Usage of econf with an additional || die
Previous by date:
Re: [RFC] PROPERTIES=set for meta-packages that should behave like package sets
Next by date:
Re: Usage of econf with an additional || die


Updated Jun 17, 2009

Summary: Archive of the gentoo-dev mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.