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: Jeroen Roovers <jer@g.o>
Subject: Re: ebuild laziness and binpkg overhead
Date: Tue, 19 Jun 2012 23:35:00 +0200
On Tue, 12 Jun 2012 23:02:40 -0400
Mike Frysinger <vapier@g.o> wrote:

> i've noticed a growing trend where people put setup of variables into 
> pkg_setup that only matter to src_* funcs presumably so they don't
> have to call the respective src_* func from an inherited eclass.
> unfortunately this adds pointless overhead to binpkgs.  can we please
> move away from this practice ?

Like this?

 * ERROR: cat/pkg-version failed (prepare phase):
 *   python_set_active_version() can be used only in pkg_setup() phase
 *
 * Call stack:
 *     ebuild.sh, line   85:  Called src_prepare
 *   environment, line 5885:  Called python_set_active_version '2'
 *   environment, line 5603:  Called die
 * The specific snippet of code:
 *           die "${FUNCNAME}() can be used only in pkg_setup() phase";
 *

Shouldn't that be in src_prepare already, or does python.eclass do
something rather important here while installing a binpkg?


     jer


References:
ebuild laziness and binpkg overhead
-- Mike Frysinger
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: ebuild laziness and binpkg overhead
Next by thread:
Re: ebuild laziness and binpkg overhead
Previous by date:
Re: Re: spec draft for cross-compile support in future EAPI (EAPI-5)
Next by date:
Re: Killing UEFI Secure Boot


Updated Jun 29, 2012

Summary: Archive of the gentoo-dev mailing list.

Donate to support our development efforts.

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