1 |
Thomas de Grenier de Latour posted |
2 |
<20041112152916.348abb9e.degrenier@×××××××××××.fr>, excerpted below, on |
3 |
Fri, 12 Nov 2004 15:29:16 +0100: |
4 |
|
5 |
> On Fri, 12 Nov 2004 22:20:29 +0900 |
6 |
> Jason Stubbs <jstubbs@g.o> wrote: |
7 |
> |
8 |
>> emerge --pretend will always show what emerge is going to do. |
9 |
> |
10 |
> Sure, but you know how users are.[] I agree that your approach is the |
11 |
> right thing to do from a reasonable semantics point of view, but from a |
12 |
> user point of view it will probably look different. |
13 |
> That said, this problem can also be solved by some cosmetic |
14 |
> means, like adding a big warning of that kind: |
15 |
> * gcc will have to be emerged twice because you lack the fortran * USE |
16 |
> flag, so if that is a problem for you, then add this flag * and you'll |
17 |
> be fine. 10 9 8 7 6 5 4 3 2 1 |
18 |
|
19 |
OK, I'm one of those "users". Read that as sysadmin of a Gentoo system. |
20 |
Sysadmin carries some responsibility for knowing how the system is set up, |
21 |
particularly as it pertains to security issues. I don't take that |
22 |
responsibility lightly, nor would I expect anyone to seriously recommend |
23 |
that I do so. |
24 |
|
25 |
I would **NOT** appreciate portage taking upon ITSELF to CHANGE my USE |
26 |
flags behind my back!!! Count this as one vote for emerge-stopping |
27 |
errors, NOT warnings that may or may not be seen in the middle of a string |
28 |
of emerges. Yes, I use pretend (or more generally, ask), and would |
29 |
normally catch a repeated emerge there. However, I still don't want use |
30 |
flags being changed out from under me. |
31 |
|
32 |
Of course, as already mentioned repeatedly, having a depend resolution |
33 |
time failure would be better than EITHER that warning or failure after a |
34 |
string of depends have been merged. I agree there (what's not to agree |
35 |
with?). However, regardless of whether that's possible, if a use flag |
36 |
needs changed, I want an error spit out to that effect, so **I** get to |
37 |
decide whether to change it or try some other package that doesn't require |
38 |
changes in my use flags. I do NOT want it simply changed, at the whim of |
39 |
portage, regardless of whether there's a big warning before it happens. |
40 |
If a use flag needs changed, *I* want to be the one changing it, on *MY* |
41 |
system. |
42 |
|
43 |
-- |
44 |
Duncan - List replies preferred. No HTML msgs. |
45 |
"They that can give up essential liberty to obtain a little |
46 |
temporary safety, deserve neither liberty nor safety." -- |
47 |
Benjamin Franklin |
48 |
|
49 |
|
50 |
|
51 |
-- |
52 |
gentoo-dev@g.o mailing list |