| 1 |
foser wrote: |
| 2 |
> On Thu, 2004-06-03 at 19:41 +0200, Marius Mauch wrote: |
| 3 |
> |
| 4 |
>>On 06/03/04 Aron Griffis wrote: |
| 5 |
>> |
| 6 |
>> |
| 7 |
>>>I'm under the impression that this is bad. Could somebody please |
| 8 |
>>>verify and explain for the sake of people on this list. This |
| 9 |
>>>particular example appears in the libxslt ebuilds, but the kde ebuilds |
| 10 |
>>>make use of a similar syntax: |
| 11 |
>>> |
| 12 |
>>> use python && inherit python |
| 13 |
>> |
| 14 |
>>Bad because it breaks the cache. Depending on the status of the python |
| 15 |
>>flag *on the rsync master* the cache settings are or are not modified by |
| 16 |
>>the python.eclass and could be completely different from the values the |
| 17 |
>>cache should have for the user. That's also the case for other cache |
| 18 |
>>variables like DEPEND, SRC_URI or SLOT, if you make them conditional on |
| 19 |
>>the environment it's likely that the cache values are wrong for some |
| 20 |
>>people. |
| 21 |
> |
| 22 |
> |
| 23 |
> The problem is that it shouldn't be a problem to do things like this, |
| 24 |
> it's portage that makes it problematic. It is not obvious why this is |
| 25 |
> problematic, so situations like these are going to pop up time and time |
| 26 |
> again. In my opinion this need to be fixed in portage, not necessarily |
| 27 |
> in the ebuilds/eclasses. And yeah, i'm talking here without any |
| 28 |
> knowledge of portage cache handling, ideal world type of talk. |
| 29 |
|
| 30 |
The problem is that all of the information in the portage cache is independent |
| 31 |
of current USE flags. The cache is simply an easier/quicker method of grabbing |
| 32 |
IUSE, DEPEND, etc. from ebuilds that doesn't involve calling bash to parse the |
| 33 |
ebuild. |
| 34 |
|
| 35 |
-- |
| 36 |
Andrew Gaffney |
| 37 |
Network Administrator |
| 38 |
Skyline Aeronautics, LLC. |
| 39 |
636-357-1548 |
| 40 |
|
| 41 |
|
| 42 |
-- |
| 43 |
gentoo-dev@g.o mailing list |
Archives