| 1 |
On 01/03/2011 09:31 PM, Jeroen Roovers wrote: |
| 2 |
> On Mon, 03 Jan 2011 16:40:57 +0200 |
| 3 |
> Samuli Suominen <ssuominen@g.o> wrote: |
| 4 |
> |
| 5 |
>> Quoting PMS, Chapter 8: |
| 6 |
>> |
| 7 |
>> "All ebuild-defined variables discussed in this chapter must be |
| 8 |
>> defined independently of any system, profile or tree dependent data, |
| 9 |
>> and must not vary depending upon the ebuild phase." |
| 10 |
>> |
| 11 |
>> http://git.overlays.gentoo.org/gitweb/?p=proj/pms.git;a=blob_plain;f=ebuild-vars.tex;hb=HEAD |
| 12 |
>> |
| 13 |
>> |
| 14 |
>> |
| 15 |
>> This is very inconvinent rule for example, github tarballs where the |
| 16 |
>> directory changes with every release. I've used this: |
| 17 |
> |
| 18 |
>> src_unpack() { |
| 19 |
>> unpack ${A} |
| 20 |
>> cd *-${PN}-* |
| 21 |
>> S=`pwd` |
| 22 |
>> } |
| 23 |
>> Far as I know, S= isn't used to generate metadata cache, so it's PMS |
| 24 |
>> that need fixing for it's wording: |
| 25 |
>> |
| 26 |
>> "All ebuild-defined variables used to generate metadata cache, |
| 27 |
>> discussed in this chapter..." |
| 28 |
> |
| 29 |
> As far as I can tell, the chapter does not mention S, but it could be |
| 30 |
> more specific. Don't see why it should, though. |
| 31 |
|
| 32 |
It's there. |
| 33 |
|
| 34 |
Chapter 8.3.: Optional Ebuild Defined Variables. It's the last one in |
| 35 |
the list. |
Archives