On Wed, Apr 27, 2005 16:08:07 PM +0200, Mathias Bauer
([EMAIL PROTECTED]) wrote:
> M. Fioretti wrote:
>
> > Nobody (not me anyway) asked to use _one_ form of package. What is
> > important is make sure that everything is always made available
> > online in "source" form, that the distributors can pick and
> > package their way for automatic installation and
> > upgrade. *Without* extra work like dissecting a self-installing
> > .sxw file to get the macro it wants to install by itself.
>
> Nobody should use sxw files for deployment. We use *UNO packages*.
Sorry for not getting back on this earlier. Thanks for the detailed
explanation, but I still have some doubts:
1) Are these UNO packages useable/recommended also for single macros,
templates, clip-art? That is, not core, serious stuff, made by
professionals?
2) Can they easily be used to create relocatable packages, that is
stuff that can either be installed once, systemwide, or in the user
home directory?
3) Where is the "official" documentation/web page explaining all this
to new, potential, one-time contributors? And *deprecating* the use
of .sxw or .sxc files as installers?
TIA,
Marco
--
Marco Fioretti mfioretti, at the server mclink.it
Fedora Core 3 for low memory http://www.rule-project.org/
The worst thing one can do is not to try, to be aware of what one
wants and not give in to it, to spend years in silent hurt wondering
if something could have materialized -- and never knowing. --
David Viscott
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
