Hi, i think it would be better to make an extra ebuild for mozilla browser only (for all the galeon users!) I send you an modified ebuild for moz 1.0-r2 with the browser only setup Greetings, Patrick
Created attachment 1423 [details] Mozilla 1.0-r2 eBuild without Mail and News Client
No. Imho, I do not think a seperate ebuild is an good idea, and will only increase complexity. If the 5/10 mins extra compile time is really that important (and the bit of disk space saved), then I really think an USE flag will be an better option.
Instead of use flags, how about an environment var similar to what is used in the Alsa ebuilds. # to build only the browser export BUILD_MOZILLA_PARTS="browser" # to build browser and mail export BUILD_MOZILLA_PARTS="browser mail"
Many people do use the mail, so if disableling it by default, you will create hassle for them, where others (like me) dont mind if it is installed. Which ever way should have mail build by default, and then have some way to disable it if you really dont want it build. My opinion anyhow.
My vote is to enable everything by default, but to use build-time environment variables to allow disabling mail and news. E.g. env NO_MAIL=YES emerge mozilla
Could work as well.
Updated 1.0-r2 with Arcady Genkin's idea.
Compilation worked, but the browser does not start for me: tea:~$ mozilla *** Failed to load overlay chrome://messenger/content/mailNavigatorOverlay.xul *** Failed to load overlay chrome://messenger/content/mailTasksOverlay.xul Warning add child failed!! Warning add child failed!! at which point the browser window comes up, but contains no buttons or anything at all (just a gray rectangle). :( I tried moving ~/.mozilla away just in case this is profile-related, but the same happens even with a vanilla profile.
What happened to the old system. Pre 1.0_rc1 of mozilla had USE options to disable/enable certain features. Why were these removed? The flags are listed at: http://www.gentoo.org/doc/use-howto.html#doc_chap2 quote... MOZILLA FLAGS mozilla -- Adds Mozilla support to other applications When emerging mozilla, you may want to keep the following flags in mind: mozaccess-builtin -- Adds to text-to-speech and eventually braille support mozctl -- Adds Pango like module to mozilla mozirc -- adds an IRC (Internet Relay Chat) module mozxmlterm -- Adds an xterm like terminal with XML support I'm in favour of using these again, plus adding mail-news to the list of available flags, since I never use the mail-news package and dont see why I should wait for it to add an extra hour compiling these extra packages I dont use.
Those USE flags are still there, although as still stated in the ebuild (please check for availible flags), they are EXPERIMENTAL. I still think that mail/news should be enabled by default, as it takes longer to recompile, than compiling the mail/news components. Ill add a "moznomail" flag as well for those that do not want it. As for moz not working without mail/news support .. works fine here. If not for you, please file a bug with the mozilla bugtrack system.
Erm... are you sure they are still there? I've had "-mozirc" in my USE variables since I found out about the flags around 0.9.9 yet 1.0 still compiles chatzilla. I'm only checking with grep on the ebuild but that should be enough to know if the flag is used, shouldnt it? toby@wataru mozilla $ grep -i 'mozirc' mozilla-1.1_beta.ebuild toby@wataru mozilla $ grep -i 'mozirc' mozilla-1.0-r1.ebuild toby@wataru mozilla $ grep -i 'mozirc' mozilla-0.9.9-r2.ebuild if [ "`use mozirc`" ] ; then toby@wataru mozilla $ Like I said before, i'm all in favour of disabling mail/news, I've never had any issues by not having it. I have no problem having it enabled by default, thats the best policy, as long as those who dont want it can turn it off. Just as a side note, it seems odd if you were to create a new flag to call it "moznomail" since the others dont have 'no' in them, and they are enabled by default too. But I see it's in the ebuild already, so it's not important, just would have kept a sense of consitancy.
As from 1.0, chatzilla is part of the default modules, sorry. If i find time in the next millenia, ill see about hacking around it.
