On 22/03/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > As I think about this more, it seems that, for example, I might just > install lame directly with portage. In that case, it'd be up to mplayer > to recognize lame's presence, yes? However, with the use flags, mplayer > is compiled with lame? > > However, if another application is *also* installed with lame as a use > flag, that'd be redundant. Or, not? They would both recursively install > lame, with lame known to both mplayer and the second app?
Lame would only be emerged one time. Use flags determine one or both of two things: 1) which packages and of what versions should be present on the system to support the desired new/updated package, and 2) what options (make config, I think) should be used when compiling those packages. You are concentrating on number one, above. For example, emerging PHP with the "cgi" use flag creates the PHP CGI binary, while the "apache2" flag will create the (forget the correct name) in-process library for Apache2. Similarly, if MySQL is aleady installed, but the "-mysql" flag is used, the PHP libraries for communicating with MySQL will not be created. Having done that, subsequently emerging phpmysql will not re-emerge Apache OR PHP, even though they are both requirements. However, I don't know what would actually happen, since the scenario above would have you with PHP on your system but without its being able to access MySQL... Best, Mickey Mullin -- [email protected] mailing list
