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: Samuli Suominen <ssuominen@g.o>
Subject: Defining S= from ebuild phase, src_unpack() ?
Date: Mon, 03 Jan 2011 16:40:57 +0200
Quoting PMS, Chapter 8:

"All ebuild-defined variables discussed in this chapter must be defined
independently of any system, profile or tree dependent data, and must
not vary depending upon the ebuild phase."

http://git.overlays.gentoo.org/gitweb/?p=proj/pms.git;a=blob_plain;f=ebuild-vars.tex;hb=HEAD



This is very inconvinent rule for example, github tarballs where the
directory changes with every release. I've used this:

src_unpack() {
	unpack ${A}
	cd *-${PN}-*
	S=`pwd`
}

In $PORTDIR/sys-fs/udisks-glue/udisks-glue-1.2.0.ebuild to get S=
defined as:

fernandotcl-udisks-glue-f9b4839

Where "f9b4839" changes...


Far as I know, S= isn't used to generate metadata cache, so it's PMS
that need fixing for it's wording:

"All ebuild-defined variables used to generate metadata cache, discussed
in this chapter..."



Replies:
Re: Defining S= from ebuild phase, src_unpack() ?
-- Ciaran McCreesh
Re: Defining S= from ebuild phase, src_unpack() ?
-- Jeroen Roovers
Re: Defining S= from ebuild phase, src_unpack() ?
-- Thomas Sachau
Re: Defining S= from ebuild phase, src_unpack() ?
-- Alex Alexander
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Can a bash script source ebuild functions?
Next by thread:
Re: Defining S= from ebuild phase, src_unpack() ?
Previous by date:
Can a bash script source ebuild functions?
Next by date:
Re: Can a bash script source ebuild functions?


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.