1 |
On Tue, 16 Nov 2004, Duncan wrote: |
2 |
> I would **NOT** appreciate portage taking upon ITSELF to CHANGE my USE |
3 |
> flags behind my back!!! Count this as one vote for emerge-stopping |
4 |
> errors, NOT warnings that may or may not be seen in the middle of a |
5 |
> string of emerges. Yes, I use pretend (or more generally, ask), and |
6 |
> would normally catch a repeated emerge there. However, I still don't |
7 |
> want use flags being changed out from under me. |
8 |
> |
9 |
> Of course, as already mentioned repeatedly, having a depend resolution |
10 |
> time failure would be better than EITHER that warning or failure after a |
11 |
> string of depends have been merged. I agree there (what's not to agree |
12 |
> with?). However, regardless of whether that's possible, if a use flag |
13 |
> needs changed, I want an error spit out to that effect, so **I** get to |
14 |
> decide whether to change it or try some other package that doesn't |
15 |
> require changes in my use flags. I do NOT want it simply changed, at the |
16 |
> whim of portage, regardless of whether there's a big warning before it |
17 |
> happens. If a use flag needs changed, *I* want to be the one changing it, |
18 |
> on *MY* system. |
19 |
|
20 |
Take your indignance somewhere else please. |
21 |
|
22 |
On Wednesday 17 November 2004 12:38, Ed Grimm wrote: |
23 |
> Agreed. If I have specified a USE flag of -<lang>, there may be a |
24 |
> reason. Given that there's no easy way to tell emerge sync to not pull |
25 |
> down any ebuilds that depend on <lang>, and to not pull down any ebuilds |
26 |
> that depend on an ebuild that depends on <lang> (, yada yada), It's very |
27 |
> easy for me to make a mistake, and select a package that is written in |
28 |
> <lang>. That doesn't mean I want it. |
29 |
|
30 |
If you read Olivier CrĂȘte's reply more closely, you'll see that he stated |
31 |
exactly the same thing and that I already ack'ed it. |
32 |
|
33 |
Regards, |
34 |
Jason Stubbs |
35 |
|
36 |
-- |
37 |
gentoo-dev@g.o mailing list |