YoYo Siska wrote: > Zac Medico wrote: > >>YoYo Siska wrote: >> >> >>>Zac Medico wrote: >>> >>> >>> >>>>More drastic than my solution but it could be >>>>necessary. I've seen USE="-*" more commonly but maybe >>>>they're equivalent. I believe emerge --nodeps does >>>>basically the same thing. >>> >>>no >>>USE="-*" skips all optional dependencies (depending on a use flag) >>>--nodeps skips ALL dependecies >>> >>> >>>yoyo >> >> >>Yeah, now I'm curious how --nodeps handles USE flags. I suppose it >>should leave them as is. Generally, the only time I use --nodeps is >>when when I encounter strange dependency issues with binary packages. > > > why should it handle USE flags in any way? > it just tels portage not to emerge the dependencie, whatever they are ( > when added by use flags..) > > that means > USE="alsa" emerge --nodeps mplayer > would (try to) compile mplayer _with_ alsa support > but in the case alsa-lib (which is an optional dep on the alsa use flag) > is no installed, it will not emerge it > (which can cause mplayer not to compile, or not to work...)
Yep, that's why --nodeps is a very special option. It depends on the way the USE flags interact with the build. I see at least 3 possible outcomes here: 1) The build fails because the it can't live without the alsa libs. 2) The build succeeds because the it can live without the alsa libs and automatically disables the alsa features. 3) The build succeeds because the alsa libs happen to already be installed. Cool ;-) Zac -- gentoo-user@gentoo.org mailing list
