1 |
Apparently, though unproven, at 16:37 on Saturday 14 May 2011, Indi did opine |
2 |
thusly: |
3 |
|
4 |
> On Sat, May 14, 2011 at 08:30:02AM +0200, Alan McKinnon wrote: |
5 |
> > Apparently, though unproven, at 05:28 on Saturday 14 May 2011, Felix |
6 |
> > Miata did |
7 |
> > |
8 |
> > opine thusly: |
9 |
> > > Is it telling me I have to change my USE from -gtk to +gtk, or can |
10 |
> > > emerging one of those 8 packages listed satisfy the dep? IOW, it's |
11 |
> > > unclear to me what "One of the following packages" actually refers to. |
12 |
> > |
13 |
> > It's telling you that you must enable USE=gtk for libcanberra for that |
14 |
> > build to succeed. The chain of packages listed won't solve the problem, |
15 |
> > they are causing it. |
16 |
> > |
17 |
> > Easiest is to list gtk in USE in make.conf, then everything that uses gtk |
18 |
> > will link against it. If you are worried about Gnome, this wil not cause |
19 |
> > gnome to be installed, just gtk+ |
20 |
> |
21 |
> True, just be aware that if you enable gtk *globally* you will end up |
22 |
> building the gtk interface for absolutely everything which has that |
23 |
> option. |
24 |
> Far better (IMO, YMMV) is to use /etc/portage/package.use specify such |
25 |
> things per package. Unless, of course, you like having a gtk GUI for |
26 |
> everything. |
27 |
> |
28 |
> :) |
29 |
|
30 |
No, it is much better to enable such a flag globally and *disable* it using |
31 |
package.use where you do *not* want it. |
32 |
|
33 |
Personally, I have better things to do than examine every new or changed |
34 |
package that shows up after avuND world and edit package.us for every single |
35 |
flag in that huge list. |
36 |
|
37 |
If a user has gtk+ installed, the common case is that they will want to use it |
38 |
globally due to gnome being present. Or they have a different WM but need gtk |
39 |
for something (eg wicd, whose kde interface sucks) and then they might as well |
40 |
just build gtk support for everything. It's not that much extra time or |
41 |
resources. |
42 |
|
43 |
There are always exceptions of course. Such as USE=ldap. It's widely used, but |
44 |
you might not want it globally enabled as USE=ldap translates to many |
45 |
different kinds of support in many different ebuilds (think of all the wildly |
46 |
varied things you could do with ldap). Dealing with each case on it's own |
47 |
merits in package.use make sense here, it's what I do. |
48 |
|
49 |
Whereas USE=gtk pretty much always translates to muchly the same thing |
50 |
everywhere - build the package so that it's gui uses that toolkit. For most |
51 |
folk, globally in make.conf makes sense. |
52 |
|
53 |
One size fits all does not work with advice on USE flags. The only thing that |
54 |
works is this: |
55 |
|
56 |
Make up your own damn mind. Your stuff is different to my stuff. |
57 |
|
58 |
;-) |
59 |
|
60 |
|
61 |
|
62 |
-- |
63 |
alan dot mckinnon at gmail dot com |