1 |
On Wednesday 18 July 2001 17:47, you wrote: |
2 |
> > No I mean when _writing_ an ebuild, I want it to do different |
3 |
> > things based on |
4 |
> > whether some packages are installed. |
5 |
> |
6 |
> But should you? I guess it really depends on the specifics of what you are |
7 |
> doing, but as a general statement I think that an ebuild shouldn't make a |
8 |
> decision on how to build a package based on the fact that I currently have |
9 |
> something installed. I think the USE variables (plus the system you |
10 |
> proposed earlier) are the Way. |
11 |
> |
12 |
> Let's say I install vorbis (to continue our earlier discussion) to play |
13 |
> around with for a while but I don't set the USE for it. I decide I don't |
14 |
> like it and unmerge it. In the meantime I've merged a bunch of audio |
15 |
> utilities that have decided to build in vorbis support and now get snivelly |
16 |
> because it's not there anymore. |
17 |
> |
18 |
> This may not be in the least applicable to the situation you are working |
19 |
> on, but I think it merits a mention.... |
20 |
> |
21 |
|
22 |
I agree. If what I suggested (i.e. interactive decisions) is implemented, |
23 |
there'll be no problems. On the other hand, while we continue to use USE |
24 |
flags, such decisions may need to be made. But what I had in mind really was |
25 |
an unusual case. |
26 |
|
27 |
-- |
28 |
|
29 |
Dan Armak |
30 |
Gentoo Linux Developer |
31 |
Matan, Israel |