Michelle Konzack wrote:
Am 2010-05-21 18:32:23, hacktest Du folgendes herunter:
I'd recommend doing a chmod -Rf o+r /path/to/sm-installdir first,
maybe also chmod a+x /path/to/sm-installdir/components if you want
to install certain global extensions.

For what?  Under UNIX/Linux a global installation is done by root.

Sure. But with a global installation the files are not run by root. The Others "group" should be able to read all files (except for confidential information, which AFAIK SM's application directory doesn't contain). From past experience I know that this is not necessarily the case after you just extracted the files. Similarly everyone should be able to access the components directory, that's why I suggested a+x. If either read or execute rights are already granted for "Others" you can skip that step of course.

For the actual installation of extensions (like localization
packages) you should change the owner of all files to your user
(chown -R yourusername /path/to/sm-installdir) temporarily, start SM
as your user, do the installation, and change back the ownership to
root.

Ehm???  The localizations are installed global an should  available  for
ALL users.  Each user should install its own copys?

No. I just assumed you knew how to accomplish that step.

You have basically two options with SM 2.0:
a) drop the XPI files that should be installed globally in the extensions directory of the application directory and start SM once. For security reasons that should not be done as root. That's why I suggested temporarily changing the ownership of all application files. b) using the --install-global-extension command line option. Use a full path and have the XPI files available on a local path to ensure it actually works. This should be relatively safe to do as root, i.e. without the need to change file ownerships.

<https://developer.mozilla.org/en/Command_Line_Options#section_51>

Neither option works with SM 1.x. Option b has been dropped after SM 2.0 so SM 2.1 will not support it anymore. Given the Add-on Manager rewrite that landed this month it might even be the case that option a won't work with SM 2.1 anymore either (cf. bug 566373 which is AFAICS limited to the extensions directory within the user's profile).

HTH

Jens

--
Jens Hatlak <http://jens.hatlak.de/>
SeaMonkey Trunk Tracker <http://smtt.blogspot.com/>
_______________________________________________
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Reply via email to