On 8/18/05, Christoph Gysin <[EMAIL PROTECTED]> wrote: > Mark Knecht wrote: > > It seems I've ended up with copies of Mozilla on the two machines I > > used to check out Unison. Apparently, at least the way I emerged it, > > the ebuild doesn't have any flags to effect this. > > Found out some more: > > You seem to have the 'gnome', 'mozilla' and 'gtk' or 'gtk2' useflag in your > make.conf. > > This is the relevant dependency tree (snipped out some stuff): > > [ebuild N ] net-misc/unison-2.12.0 +gtk +gtk2 > [ebuild N ] dev-ml/lablgtk-2.4.0 +gnome > [ebuild N ] gnome-base/gnome-panel-2.10.2 > [ebuild N ] gnome-extra/evolution-data-server-1.2.3 +mozilla > [ebuild N ] www-client/mozilla-1.7.11 > > You advised portage to build unison, which needs lablgtk. lablgtk gets built > with gnome-support, so it needs gnome-panel, which in turn needs > evolution-data-server. And since you have the global useflag mozilla, this > will > pull mozilla in. > > Right? (could also be some other combination of use-flags, you get the idea) > > Christoph
Christoph, Hi, I think you're basically right but this is a case where the real meaning of flags is important? My understanding of the 'mozilla' flag was that it instructed apps to build in support for Mozilla and not that it required Mozilla to get emerged. My real thought here is not that I really want 'mozilla' support in Unison but if any app needs a browser that it should be happy with Firefox instead of any other app. I could look at removing the global mozilla flag and using it only on certain apps, but really I'm wondering why Unison didn't accept Firefox as a browser and wondering if the ebuild for it, or more likely evolution-data-server, could be improved in that area. thanks, Mark > -- [email protected] mailing list
