В Вск, 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.
Peter Volkov wrote:
В Вск, 28/09/2008 в 20:24 +0200, Thomas Sachau пишет:
I see many ebuild that still use econf || die, also econf should die by
itself.
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
Ben de Groot wrote:
So, can we have a nice little table of which functions die by themselves
and which ones need || die added in ebuilds? Please?
Thanks,
A quick grep of /usr/lib/portage/bin clues you in that every function
that is an external file does *not* die by itself. So, emake, do*,
On Tue, 30 Sep 2008 15:10:44 +
Daniel Gryniewicz (dang) [EMAIL PROTECTED] wrote:
dang08/09/30 15:10:44
Modified: package.mask
Log:
Remove poppler from mask; current evince works fine
s/current/only/
I currently have pdftex,luatex xpdf failing here. It would
Jeremy Olexa schrieb:
Ben de Groot wrote:
So, can we have a nice little table of which functions die by themselves
and which ones need || die added in ebuilds? Please?
Thanks,
A quick grep of /usr/lib/portage/bin clues you in that every function
that is an external file does *not* die
Nirbheek Chauhan kirjoitti:
On Sat, Sep 27, 2008 at 3:47 PM, Thomas Sachau [EMAIL PROTECTED] wrote:
So what about this one?
default_src_install() {
if [ -f Makefile ] || [ -f GNUmakefile ] || [ -f makefile ]; then
emake DESTDIR=${D} install || die emake install failed
On Dienstag, 30. September 2008, Thomas Sachau wrote:
From my knowledge and experience with sunrise:
some functions that dont need || die:
epatch, econf, eqmake3, eqmake4
some functions that need || die:
emake, do*
Afaik die wont work in a subshell independent of how it is called, so the
On Mon, 29 Sep 2008 22:31:46 -0700
Zac Medico [EMAIL PROTECTED] wrote:
Can package.use syntax be extended to allow set entries?
@compiz-fusion -gnome kde kde4
Perhaps, but we need to clarify how that sort of setting will affect
nested sets. For example, if @compiz-fusion contains nested
