I've upgraded to the new mozilla 1.7 just to realize that all my scripts that use mozilla are broken by this mozilla-launcher stuff.
IMHO, this means that mozilla-launcher isn't transparent as a forced option should be.
Is there any reason for why this mozilla-launcher script isn't a USE option?
Steps to Reproduce:
The reason for mozilla-launcher is that the base mozilla scripts are broken because they don't support running firefox/mozilla/thunderbird simultaneously. xremote commands will go to whichever is found first. It's completely random.
In recent versions of moz/ff/thunderbird this is fixed (finally!) by the -a option to mozilla-xremote-client. mozilla-launcher recognizes this and uses -a transparently.
What scripts that you use are broken by mozilla-launcher? I believe that everything should work and would appreciate your pointing out anything that does not.
I use a few scripts that fix this problem and make it easier for me to open URL in a tab or a new window. I know it's basically what mozilla-launcher does, but I don't see why I can't use my own script. Here's an example:
mozilla -remote "ping()" &> /dev/null
if [ $? == "0" ]; then
exec mozilla -remote "openURL($1,new-tab)"
exec mozilla $1
This doesn't work with mozilla-launcher. I think it's because mozilla-launcher doesn't return non-zero values, as one would expect with the ping() command.
Can't you just copy your script into /usr/bin after each merge? That's basically what you'd have done before, right?
actually no. I call it mozilla-tab so I don't have to mess up the default stuff.
Anyway, the point here is not my script...the point is that if mozilla-launcher is default it should not break scripts or programs that expect mozilla to act the way it normally acts.
Another side effect of this is that we may start seeing mozilla-launcher only apps, which is really bad.
"The reason for mozilla-launcher is that the base mozilla scripts are broken because they don't support running firefox/mozilla/thunderbird simultaneously."
That's a weak assumption for its requirement imo. In my case, I _only_ use Mozilla. As a result, I'm dependent on mozilla-launcher, and if it breaks, I can't start Mozilla.
My suggestion would be to create a USE flag for mozilla-launcher, set it by default to flagged when nothing exists in /etc/make.conf to negate it, and make a strict warning not to unset it unless you know what you're doing.
If mozilla-launcher weren't a dependency then the mozilla ebuild itself would place a script in /usr/bin on its own by necessity, which you would then might have to replace.
I'm not sure how the use case is different either way; if no mozilla-launcher, you have to use your own script, and if there is one you have to use your own script.
There is no guarantee the upstream script will correctly honor the way your mozilla-tab script is calling it forever. I recommend specifically calling /usr/lib/mozilla/mozilla in your script, which would allow it to be placed alongside mozilla-launcher with no problem.