1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA256 |
3 |
|
4 |
Hi folks, |
5 |
|
6 |
i've some packages fetching SRC_URI from github.com |
7 |
tarballs/tags/files like x11-misc/trayer-srg. |
8 |
|
9 |
Fortunately, github.com provides (mostly) stable tarballs that are fit |
10 |
for manifestations (file sizes and checksums don't change). |
11 |
There is no need to create/host tarballs to be picked up by mirrors. |
12 |
|
13 |
Unfortunately, these tarballs contain $author-$repository-$commitidabrev |
14 |
(e.g. sargon-trayer-srg-5353f80) ad top directory. |
15 |
|
16 |
One approach is to define ${S} to match these additional data, but to |
17 |
easy version bumps, I've started to rename the extracted directory |
18 |
within src_unpack, to avoid mentioning the $author, $commitid and |
19 |
modifying ${S}. |
20 |
|
21 |
""" |
22 |
SRC_URI="https://github.com/sargon/${PN}/tarball/${P/-srg/} -> |
23 |
${P}.tar.gz" |
24 |
|
25 |
src_unpack() { |
26 |
unpack ${A} |
27 |
mv *-${PN}-* ${P} || die |
28 |
} |
29 |
""" |
30 |
|
31 |
I wonder if others have similar workarounds? |
32 |
|
33 |
And does this src_unpack qualify for an eclass or being added to an |
34 |
existing one, to avoid code replication? |
35 |
|
36 |
Maybe fetch filename " -> ${P}.tar.gz" can be mangled into SRC_URI by |
37 |
this eclass/function, too. |
38 |
|
39 |
Michael |
40 |
|
41 |
- -- |
42 |
Gentoo Dev |
43 |
http://xmw.de/ |
44 |
|
45 |
-----BEGIN PGP SIGNATURE----- |
46 |
Version: GnuPG v2.0.17 (GNU/Linux) |
47 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ |
48 |
|
49 |
iF4EAREIAAYFAk/V9YwACgkQknrdDGLu8JBbzgD/aZ0USZEnfa2bQaoHOjKglMN/ |
50 |
BJHuAOv0At95B4ARSXkA/A79qARFSCCAryjv55A1f6+3LafaRJlP0QKLp+zHoKvq |
51 |
=W1YG |
52 |
-----END PGP SIGNATURE----- |