I look forward to seeing this, right now I find the updater very
confusing. A question though, if run as root under cron would it still
need the sudo password?
On 9/4/2013 9:09 AM, Szládovics Péter wrote:
2013-09-04 13:42 keltezéssel, Martin Rabl írta:
Hi,
Am 04.09.13 08:37, schrieb Anna Christina Naß:
It would be great if you could provide some more documentation on it,
especially on:
- what do the options in the files
defaults/preferences/*.js
chrome/content/extensions.rdf
mean?
Ignore them. ;-)
If not:
- default/preferences holds all default preferences a TB-Plugin use
when it starts the first time - nice for preconfiguration, but not
often needed, I think. This preferences will be overridden after set
the user settings.
(the *.js files will all be read and interpreted from the gecko/XUL
machine, I think, alphabetically)
- extensions.rdf: Pls. have a look at
https://developer.mozilla.org/en-US/docs/Install_Manifests
https://developer.mozilla.org/en-US/docs/Extension_Versioning,_Update_and_Compatibility
It's not enough...
You need an update site too for correct functionality. I'm working on
a self-configured build site:
You give some parameters on a web form, and will receive a script in
email. You save the script to the server what is hosted the SOGo
WebUI, and just run it with normal user privileges.
It will configure your update site (if needed), download the most
fresh git sources from Inverse, set up the Integrator parameters,
build the xpi files (Integrator and Connector too) and set up the
update site code for fresh builds (file names, versions, etc.).
If you run it again at the future, it will refresh the plugins - do
not run it under cron, because it will need the password for sudo.
Only use it with commandline.
So, please a little patience :)
--
users@sogo.nu
https://inverse.ca/sogo/lists
