| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
On Friday 04 June 2004 03:53, foser wrote: |
| 5 |
> On Thu, 2004-06-03 at 19:41 +0200, Marius Mauch wrote: |
| 6 |
> > On 06/03/04 Aron Griffis wrote: |
| 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 |
> The problem is that it shouldn't be a problem to do things like this, |
| 23 |
> it's portage that makes it problematic. It is not obvious why this is |
| 24 |
> problematic, so situations like these are going to pop up time and time |
| 25 |
> again. In my opinion this need to be fixed in portage, not necessarily |
| 26 |
> in the ebuilds/eclasses. And yeah, i'm talking here without any |
| 27 |
> knowledge of portage cache handling, ideal world type of talk. |
| 28 |
|
| 29 |
Three options: |
| 30 |
|
| 31 |
1) Drop portage caching altogether. |
| 32 |
2) Separate the global section into a separate non-bash file with new syntax. |
| 33 |
3) Make everything constant in the global section of ebuilds. |
| 34 |
|
| 35 |
#1 is definately not acceptable at this stage as dep calculation time would |
| 36 |
take about 50 times as long. #2 is probably the best but offers no short term |
| 37 |
solution. Which leaves #3. |
| 38 |
|
| 39 |
Most dynamic stuff should be able to be done in pkg_setup(). Anybody who has |
| 40 |
more specific requirements should jump into #gentoo-portage to discuss them |
| 41 |
and find a better solution. |
| 42 |
|
| 43 |
Regards, |
| 44 |
Jason Stubbs |
| 45 |
-----BEGIN PGP SIGNATURE----- |
| 46 |
Version: GnuPG v1.2.4 (GNU/Linux) |
| 47 |
|
| 48 |
iQCVAwUBQL+m2VoikN4/5jfsAQL8WAQAumFPjUTeSmvvgHw5GZCV2jc+4DkFoWq/ |
| 49 |
/bfuDkY4iN2n5Y/pBTTNyXnmkOn86NxFtQ0KuvBcZfK3TcitoBt7KHZNmCFi5xWD |
| 50 |
Q9EvEvId1iBfAePS2m0UR3zbP6cKSYz0qWs+0hHo5fgMhaCQFe3j36SNZxLbDTSA |
| 51 |
qpspNWdtdG4= |
| 52 |
=daDu |
| 53 |
-----END PGP SIGNATURE----- |
| 54 |
|
| 55 |
-- |
| 56 |
gentoo-dev@g.o mailing list |
Archives