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
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
To: gentoo-dev@g.o
From: Michael Weber <xmw@g.o>
Subject: tarballs eclass idea
Date: Mon, 11 Jun 2012 15:41:33 +0200
Hash: SHA256

Hi folks,

i've some packages fetching SRC_URI from
tarballs/tags/files like x11-misc/trayer-srg.

Fortunately, provides (mostly) stable tarballs that are fit
for manifestations (file sizes and checksums don't change).
There is no need to create/host tarballs to be picked up by mirrors.

Unfortunately, these tarballs contain $author-$repository-$commitidabrev
(e.g. sargon-trayer-srg-5353f80) ad top directory.

One approach is to define ${S} to match these additional data, but to
easy version bumps, I've started to rename the extracted directory
within src_unpack, to avoid mentioning the $author, $commitid and
modifying ${S}.

SRC_URI="${PN}/tarball/${P/-srg/} ->

src_unpack() {
    unpack ${A}
    mv *-${PN}-* ${P} || die

I wonder if others have similar workarounds?

And does this src_unpack qualify for an eclass or being added to an
existing one,  to avoid code replication?

Maybe fetch filename " -> ${P}.tar.gz" can be mangled into SRC_URI by
this eclass/function, too.


- --
Gentoo Dev

Version: GnuPG v2.0.17 (GNU/Linux)
Comment: Using GnuPG with Mozilla -


Re: tarballs eclass idea
-- PaweĊ‚ Hajdan, Jr.
Re: tarballs eclass idea
-- Ian Whyman
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Automated Package Removal and Addition Tracker, for the week ending 2012-06-10 23h59 UTC
Next by thread:
Re: tarballs eclass idea
Previous by date:
Re: gtk3 useflag and support of older toolkits
Next by date:
Repoman check before file stable request

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.