1 |
cat /usr/portage/profiles/base/packages - and all will be revealed :) |
2 |
|
3 |
All profiles should inherit from this - but may provide their own |
4 |
modifications - e.g. |
5 |
|
6 |
/usr/portage/profiles/arch/sparc/packages adds sparc-utils to @system |
7 |
on that set of platforms. |
8 |
|
9 |
Cheers, |
10 |
malc. |
11 |
|
12 |
On Fri, Mar 5, 2010 at 1:44 AM, Mark Knecht <markknecht@×××××.com> wrote: |
13 |
> On Thu, Mar 4, 2010 at 3:23 PM, Paul Hartman |
14 |
> <paul.hartman+gentoo@×××××.com> wrote: |
15 |
>> On Thu, Mar 4, 2010 at 4:23 PM, Mark Knecht <markknecht@×××××.com> wrote: |
16 |
>>> On Thu, Mar 4, 2010 at 11:13 AM, Paul Hartman |
17 |
>>> <paul.hartman+gentoo@×××××.com> wrote: |
18 |
>>>> On Thu, Mar 4, 2010 at 12:22 PM, Mark Knecht <markknecht@×××××.com> wrote: |
19 |
>>>>> I would like emerge -epv @system to be a fairly contained set of |
20 |
>>>>> packages. (If possible like it was when I first built the system a |
21 |
>>>>> mere 5 weeks ago...) It seems out of control on my system these days |
22 |
>>>>> as it wants to emerge 242 packages. One major contributor is not using |
23 |
>>>>> a global -cups use flag in make.conf which would reduce it to 178. |
24 |
>>>>> That was added to figure out why Gnome didn't see Sups printers at |
25 |
>>>>> all. Sure, I would then have to turn on cups for certain packages but |
26 |
>>>>> that's OK with me. However I still see cairo, icedtea-bin, virtual |
27 |
>>>>> java stuff, alsa-libs, and a bunch of x11-proto files so it doesn't |
28 |
>>>>> feel like @system stuff to me |
29 |
>>>>> |
30 |
>>>>> 1) Where is the 'system' or '@system' specification on my machine? |
31 |
>>>>> |
32 |
>>>>> 2) If you folks run emerge -epv @system then how machine packages do you see? |
33 |
>>>> |
34 |
>>>> I believe it all depends on the profile you're using. If you're using |
35 |
>>>> a desktop profile maybe that's why it's calling in GUI toolkits and |
36 |
>>>> stuff... |
37 |
>>>> |
38 |
>>> |
39 |
>>> Thanks Paul. I hadn't thought of that and I think you're correct. I |
40 |
>>> played a bit with changing profiles and then looking at what emerge |
41 |
>>> -epv @system would or would not do. It's clearly related. |
42 |
>>> |
43 |
>>> In the end I wonder if this is a lost cause? If the packages I run |
44 |
>>> really require these flags then they are all going to get built the |
45 |
>>> same way. I'd prefer that @system was simple and that @world showed |
46 |
>>> how I had changed the system to meet my needs, but I'm not sure it's |
47 |
>>> worth the effort at this point to get there. |
48 |
>> |
49 |
>> Looking in the current desktop profile, it shows this: |
50 |
>> |
51 |
>> USE="a52 aac acpi alsa branding cairo cdr dbus dts dvd dvdr eds emboss |
52 |
>> encode evo fam firefox flac gif gnome gpm gstreamer gtk hal jpeg kde |
53 |
>> ldap libnotify mad mikmod mng mp3 mp4 mpeg ogg opengl pdf png ppds |
54 |
>> qt3support qt4 quicktime sdl spell svg thunar tiff truetype vorbis |
55 |
>> win32codecs unicode usb X x264 xml xulrunner xv xvid" |
56 |
>> |
57 |
>> So support for things like gnome, gtk, kde and qt4 are there by |
58 |
>> default. I guess you could take the above list, put a - in front of |
59 |
>> the ones you don't think you want and put it in make.conf and see what |
60 |
>> happens. :) |
61 |
>> |
62 |
>> |
63 |
> Yeah, that's interesting and to some extent anyway probably involved |
64 |
> with why I'm getting a lot of the package I get. What I'm not |
65 |
> understanding yet is what packages themselves are in @system. Where do |
66 |
> those come from? I'm assuming that because of all these flags some |
67 |
> system packages then require more and more support packages as an |
68 |
> avalance, but I'm not understanding what list of packages gets the |
69 |
> whole things started. |
70 |
> |
71 |
> @world is /var/lib/portage/world. |
72 |
> |
73 |
> @system is ? |
74 |
> |
75 |
> Thanks, |
76 |
> Mark |
77 |
> |
78 |
> |