1 |
On Fri, Sep 16, 2005 at 08:53:10PM -0700, maxim wexler wrote |
2 |
|
3 |
> > Differs from both of yours again. Here's my |
4 |
> > package.use for the machine: |
5 |
> > |
6 |
> > dragonfly ~ # cat /etc/portage/package.use |
7 |
> |
8 |
> no such file on my machine. Did I miss something? |
9 |
|
10 |
package.use is a file where you can turn USE flags on or off *FOR |
11 |
INDIVIDUAL PACKAGES*. Here's mine... |
12 |
|
13 |
|
14 |
app-misc/mc -X |
15 |
app-office/openoffice-bin java |
16 |
app-text/xpdf motif |
17 |
media-gfx/gimp doc exif |
18 |
media-libs/win32codecs real |
19 |
media-video/mplayer custom-cflags i8x0 real sse2 3dnowext mmxext |
20 |
net-misc/wget ssl |
21 |
net-nntp/slrn uudeview |
22 |
sys-libs/glibc userlocales |
23 |
www-client/links svga |
24 |
sys-apps/busybox static |
25 |
|
26 |
|
27 |
There are some options that certain packages *MUST* have, while other |
28 |
packages *MUST NOT* have them. E.g. busybox is a "rescue package". It |
29 |
is most likely going to be required when libraries are screwed up. So |
30 |
it needs static linking, which is a bad idea for most apps. I use mc |
31 |
(Midnight Commander) mostly in text consoles. It has weird interaction |
32 |
with X. I therefore turn off X support for mc. svga pounds away |
33 |
directly at IO ports, and requires setuid root (or else run an app as |
34 |
root). It's OK with links, but I don't want it in my global USE var, |
35 |
because then a whole bunch of other apps, besides links, will start |
36 |
requiring setuid. |
37 |
|
38 |
Additionally, check /usr/portage/profiles/use.local.desc for |
39 |
package-specific flags. /etc/portage/package.use is where those flags |
40 |
should go. |
41 |
|
42 |
> This is all I got: |
43 |
> USE="java alsa esd mad mp3 ogg oss vorbis xmms" |
44 |
> |
45 |
> Assembling these flags has been hit or miss. Something I read in a |
46 |
> forum somewhere or just a guess. It certainly doesn't represent all |
47 |
> the software I've emerged since setting up this system about 4 months |
48 |
> ago. Is there some sort of tried and true method of determining what |
49 |
> USE flags to use. |
50 |
|
51 |
cat /proc/cpuinfo |
52 |
|
53 |
on your machine, and post the output on this list. That'll let us know |
54 |
what CFLAGS and USE flags your cpu supports. And of course, a lot |
55 |
depends on what programs you're running on your machine. |
56 |
|
57 |
-- |
58 |
Walter Dnes <waltdnes@××××××××.org> |
59 |
My musings on technology and security at http://tech_sec.blog.ca |
60 |
-- |
61 |
gentoo-user@g.o mailing list |