Missing Mozilla Module for SuSEconfig
I updated Mozilla to the 1.2.1 version from SuSE's Projects ftp site, using the SuSE 8.0 version on my SuSE 8.1 system in order to get working Java plugins. (I also updated Galeon as well...) Now I get: bronxville:/home/rocks # SuSEconfig --module mozilla Starting SuSEconfig, the SuSE Configuration Tool... Running module mozilla only Reading /etc/sysconfig and updating the system... Module mozilla does not exist Finished. bronxville:/home/rocks # Should I be concerned? How do I regenerate the file? Thanks! -- ___________________________________________________________________ A Message From... L. Mark Stone http://www.lmstone.com
Hi, On 7 Feb 2003, L. Mark Stone wrote:
Now I get: bronxville:/home/rocks # SuSEconfig --module mozilla Starting SuSEconfig, the SuSE Configuration Tool... Running module mozilla only Reading /etc/sysconfig and updating the system... Module mozilla does not exist Finished. bronxville:/home/rocks #
Should I be concerned? How do I regenerate the file?
since 1.2.1 there is no longer a SuSEconfig module for mozilla. All needed registration of the components is done in the RPM scripts. This is possible because SuSE is using another install-mechanism since SuSE Linux 8.1 where it is finally possible to use post-scripts. Sincerely, Wolfgang Rosenauer
Hi, Wolfgang Rosenauer schrieb:
On 7 Feb 2003, L. Mark Stone wrote:
Now I get: bronxville:/home/rocks # SuSEconfig --module mozilla Starting SuSEconfig, the SuSE Configuration Tool... Running module mozilla only Reading /etc/sysconfig and updating the system... Module mozilla does not exist Finished. bronxville:/home/rocks #
Should I be concerned? How do I regenerate the file?
since 1.2.1 there is no longer a SuSEconfig module for mozilla. All needed registration of the components is done in the RPM scripts. This is possible because SuSE is using another install-mechanism since SuSE Linux 8.1 where it is finally possible to use post-scripts.
But what to do when installing a new plug-in, e. g. a new java? Do I have to to it on my own again? This is okay, but why... Ré
On Tue, 11 Feb 2003, René Matthäi wrote:
But what to do when installing a new plug-in, e. g. a new java? Do I have to to it on my own again? This is okay, but why...
if you install SuSE RPMs it should be done automatically because we use RPM triggers for that case. If you install plugins on your own you have to take care for them. CU, Wolfgang Rosenauer
Hi, thank you for your prompt answer! Wolfgang Rosenauer schrieb:
On Tue, 11 Feb 2003, René Matthäi wrote:
But what to do when installing a new plug-in, e. g. a new java? Do I have to to it on my own again? This is okay, but why...
if you install SuSE RPMs it should be done automatically because we use RPM triggers for that case. If you install plugins on your own you have to take care for them.
But after all, it would have been very useful and easy for a lot of us if there remained the possibility to have SuSEconfig.mozilla look for certain plug-ins and integrate it in mozilla. I can only repeat my example with a new Java Runtime. I would just have to modify the /usr/lib/java link and SuSEconfig would do the neccessary for mozilla. In this special case it would be useful then if the postinstall scripts of mozilla would use /usr/lib/java instead of linking directly to /usr/lib/SunJava2/jre So far I can only speak for myself, but the SuSEconfig.mozilla modul was a good idea and until now well implemented... Regards, René Matthäi
But after all, it would have been very useful and easy for a lot of us if there remained the possibility to have SuSEconfig.mozilla look for certain plug-ins and integrate it in mozilla. I can only repeat my example with a new Java Runtime. I would just have to modify the /usr/lib/java link and SuSEconfig would do the neccessary for mozilla. In this special case it would be useful then if the postinstall scripts of mozilla would use /usr/lib/java instead of linking directly to /usr/lib/SunJava2/jre So far I can only speak for myself, but the SuSEconfig.mozilla modul was a good idea and until now well implemented...
The Mozilla and Phoenix packages from www.usr-local-bin.org include SuSEconfig modules that setup the plugins. Also, when Mozilla 1.3 comes out, I'm going to be reintroducing GTK1 builds for those who don't want to run the gauntlet with the GTK2 builds. They'll be two separate package names - mozilla[-mail|irc|devel etc] and mozilla-gtk2[-devel] so you can have a nice, stable version of Mozilla, and a bleeding edge GNOME2 Galeon if you so desire. -- James Ogley, Webmaster, Rubber Turnip james@rubberturnip.org.uk http://www.rubberturnip.org.uk Jabber: riggwelter@myjabber.net Using Free Software since 1994, running GNU/Linux (SuSE 8.1) GNOME updates for SuSE: http://www.usr-local-bin.org
In a previous message, James Ogley wrote:
They'll be two separate package names - mozilla[-mail|irc|devel etc] and mozilla-gtk2[-devel] so you can have a nice, stable version of Mozilla, and a bleeding edge GNOME2 Galeon if you so desire.
I'm slightly confused - do you mean that the mozilla builds will be gtk1, whereas the -devel rpm only will also be available as gtk2? That's a shame if so! John -- John Pettigrew Headstrong Games john@headstrong-games.co.uk Fun : Strategy : Price http://www.headstrong-games.co.uk/ Board games that won't break the bank Knossos: escape the ever-changing labyrinth before the Minotaur catches you!
I'm slightly confused - do you mean that the mozilla builds will be gtk1, whereas the -devel rpm only will also be available as gtk2? That's a shame if so!
No, cos that would be utterly useless, there'll be mozilla and mozilla-gtk2 Both will have the relevant -devel package. -- James Ogley, Webmaster, Rubber Turnip james@rubberturnip.org.uk http://www.rubberturnip.org.uk Jabber: riggwelter@myjabber.net Using Free Software since 1994, running GNU/Linux (SuSE 8.1). GNOME updates for SuSE: http://www.usr-local-bin.org
In a previous message, James Ogley wrote:
do you mean that the mozilla builds will be gtk1, whereas the -devel rpm only will also be available as gtk2?
No, cos that would be utterly useless, there'll be mozilla and mozilla-gtk2
That's alright, then :-) John -- John Pettigrew Headstrong Games john@headstrong-games.co.uk Fun : Strategy : Price http://www.headstrong-games.co.uk/ Board games that won't break the bank Valley of the Kings: ransack an ancient Egyptian tomb but beware of mummies!
Hi, On Tue, 11 Feb 2003, René Matthäi wrote:
if you install SuSE RPMs it should be done automatically because we use RPM triggers for that case. If you install plugins on your own you have to take care for them.
But after all, it would have been very useful and easy for a lot of us if there remained the possibility to have SuSEconfig.mozilla look for certain plug-ins and integrate it in mozilla. I can only repeat my example with a new Java Runtime. I would just have to modify the /usr/lib/java link and SuSEconfig would do the neccessary for mozilla. In this special case it would be useful then if the postinstall scripts of mozilla would use /usr/lib/java instead of linking directly to /usr/lib/SunJava2/jre So far I can only speak for myself, but the SuSEconfig.mozilla modul was a good idea and until now well implemented...
The script is still there (/opt/mozilla/add-plugins.sh) but not called automatically when SuSEconfig is running. I think this is a compromise? It was always a problem for many people that SuSEconfig has to run after a mozilla update. But I always want feedback, what can be done better. CU, Wolfgang Rosenauer
participants (5)
-
James Ogley -
John Pettigrew -
L. Mark Stone -
René Matthäi -
Wolfgang Rosenauer