1 |
On 09/21/2012 01:26 PM, Pacho Ramos wrote: |
2 |
> El vie, 21-09-2012 a las 12:45 -0700, Zac Medico escribió: |
3 |
>> On 09/21/2012 12:08 PM, Pacho Ramos wrote: |
4 |
>>> Hello |
5 |
>>> |
6 |
>>> This comes from this gentoo-dev thread: |
7 |
>>> http://www.gossamer-threads.com/lists/gentoo/dev/260536 |
8 |
>>> |
9 |
>>> In that one, we try to use the following: |
10 |
>>> has vala ${IUSE//+/} && ! use vala && return 0 |
11 |
>>> |
12 |
>>> as already done in many eclasses/ebuilds. The problem is that Ciaran |
13 |
>>> wants to forbid it because he says it's not specified in PMS. My |
14 |
>>> suggestion was to simply specify it as it's currently implemented in |
15 |
>>> portage because that functionality is (apart of needed) being used for a |
16 |
>>> long time in the tree by numerous eclasses/ebuilds, then, from my point |
17 |
>>> of view, wouldn't be any sense on lose time for moving them to current |
18 |
>>> functionality to a worse one, wait for the next eapi and, finally, |
19 |
>>> revert them back to current behavior. |
20 |
>>> |
21 |
>>> The problem is that I cannot find any doc about how this is currently |
22 |
>>> handled in portage. Could you help me on it please? |
23 |
>> |
24 |
>> That `has vala ${IUSE//+/}` thing should work for all versions of |
25 |
>> portage that have existed since PMS came around. The way that it works |
26 |
>> is that that ebuild.sh sources the ebuild, and the inherit function |
27 |
>> makes temporary backups of IUSE so that the IUSE settings from all of |
28 |
>> the eclasses and the ebuild can be stacked together after the sourcing |
29 |
>> is complete. The stacked IUSE value that's generated then remains in the |
30 |
>> ebuild's environment for all phases. |
31 |
> |
32 |
> Thanks a lot, do you let me send your reply to gentoo-dev ML? |
33 |
|
34 |
Sure. :) |
35 |
-- |
36 |
Thanks, |
37 |
Zac |