> > What would be really great would be to bea able to do this... > > > > emerge mozilla-complete > > > > ...and have it do all this stuff for you. > > maybe this is a bit overdoing it, or maybe just wishful thinking, > but it seems > that the USE flags are getting a bit crazy in an attempt to solve > this sort > of thing. want flash in konqueror USE="motif" etc. etc. > > why not something like this? have the USE flags for standard > things, like X > support. you don't want a bunch of gtk or qt stuff on your sever > just 'cause > you like nmap right? > > but for more detailed things, like flash in konqueror or > realplayer plugins in > mozilla, why not a basic yes/no question period?: > > # emerge -p mozilla > Do you want flash? y > Do you want real player? y > Do you want <some sucky plugin>? n > ...compiling list > > [ebuild N ] net-www/mozilla-1.3-r2 > [ebuild N ] net-www/netscape-flash-6.0.79 > [ebuild N ] media-video/realplayer-8-r5 >
I like the concept of the idea, but how would the ebuild for Mozilla know about all possible plug-in and add ons? New data type may come along after the ebuild is written, and as a user I don't even know about it until I run into the data type on the web. I can see the logic of how M$ does it: 1) You browse until you have a problem. 2) A dialog pops up and say I need something, based on a certain data type. IE6 offers to download something. Mozilla offers to save the file. 3) At this point, if there was a link to some web page that has known associations and what needs to be downloaded/emerged to use the data type, then I could open a xterm and as root go make it happen. -- [EMAIL PROTECTED] mailing list
