1 |
Peter Stuge posted on Sun, 17 Jun 2012 00:16:36 +0200 as excerpted: |
2 |
|
3 |
> Duncan wrote: |
4 |
>> users would unmerge ppp if they knew about it when they no longer |
5 |
>> needed it, but knowing about it is the problem. |
6 |
> |
7 |
> Sorry, but what is the connection to a USE flag? |
8 |
> |
9 |
> I agree that knowing about it is the problem. I don't think that knowing |
10 |
> about a package is different from knowing about a USE flag. |
11 |
|
12 |
USE flags show up (with the recommended -v anyway) pre-merge, where |
13 |
people can see and deal with them (doing equery u <pkg> or whatever if |
14 |
they need more information about the flag) upfront. |
15 |
|
16 |
post-pkg-install messages appear at the tail end, and even for people |
17 |
like me that are quite religious about reading such things, if a big |
18 |
system update crashes the entire system (I've been dealing with hardware |
19 |
issues lately so this is fresh in mind), messages for already merged at |
20 |
time of crash packages won't be shown when a new update is run after |
21 |
reboot. |
22 |
|
23 |
So USE flags tend to be much more visible/discoverable. =:^) |
24 |
|
25 |
> Sets look nice though! :) |
26 |
|
27 |
I just wish whatever PMS or other issues would get worked out, so the |
28 |
feature could start benefiting normal users, not just those brave enough |
29 |
to run a masked portage. =:^( I've been using sets since kde 4.2 when I |
30 |
migrated to kde4 at least, three years ago now, without major issue |
31 |
(there was a minor issue when certain sets parameters changed a year or |
32 |
two ago, but that's par for the course when using experimental features), |
33 |
and the technology really is reasonably mature and proven now. It just |
34 |
needs to be available for ordinary gentooers... |
35 |
|
36 |
-- |
37 |
Duncan - List replies preferred. No HTML msgs. |
38 |
"Every nonfree program has a lord, a master -- |
39 |
and if you use the program, he is your master." Richard Stallman |