Zac Medico wrote: >> YoYo Siska wrote: > >>>> >>>>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. >>
I have a real example that illustrates (2) above: USE=-nomotif emerge --nodeps xpdf If motif isn't installed (or the headers aren't linked properly by motif-config), the build completes successfully with motif disabled. The ebuild tells the configure script to enable motif because of the USE=-nomotif flag but then later the configure script doesn't detect the motif headers and continues the build anyways without motif. Zac -- gentoo-user@gentoo.org mailing list
