Hi,
M. Fioretti wrote:
Does it explain how to create stuff that doesn't create problems to Linux distributors (in the sense explained at the beginning of this thread)? That is, how to provide stuff that can be directly used by others to create native Linux packages in whatever format?
I think Linux distributors should figure out if there is anything that provents them from wrapping UNO packages into native packages. I would imagine that to be rather simple.
2.0 mechanism allow you to add add-on very simply to your installation, and the most important, without restarting OOo, under tools/package manager.
The latter only works when you install as a user for that user, not when installing system-/installation-wide.
Er, yes, here is the problem again. This is exactly what I mentioned as a pain for Linux distributors when I started this thread. More exactly, the pain is if add-ons are _only_ distributed as OO.o native packages: and if Linux users are not recommended to prefer, whenever available, the native packages for their distribution.
Why should Linux *users* be told this.
As you (or Nicolas) said, Linux administrators will probably prefer that anyhow and Linux distributors will surely only distribute addons wrapped in native packages. If distros describe how to do this for their package manager, administrators can probably easily create their own native packages wrappers for UNO packages that the author does not provide in this form. But for Linux users that are not also administrators, native packages don't work. On single-owner Linux machines, where the user is also an administrator, the owner is free to choose whether she prefers unified system-wide package management or easy GUI install of packages - particularly for packages which the author does not provide as native packages for their distro.
If administrators want to disallow that users install their own add-ons, that is a separate issue. This is probably possible by changing some OOo configuration.
Ciao, J�rg
-- Joerg Barfurth Sun Microsystems - Desktop - Hamburg >>>>>>>>>>>>>>>>>> using std::disclaimer <<<<<<<<<<<<<<<<<<<<<<< Software Engineer [EMAIL PROTECTED] OpenOffice.org Configuration http://util.openoffice.org
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
