Hi,
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.
Do you know what an UNO package is ? Do you know the difference between user and share OOo subdirectories ?
IMHO, the actual package designs + the GUI possibilbilty of deploying fullfills all the needs
And as it has already been said (mathias ?) if it is a corporate policy not to install extra addons, let admins do their job and remove the menu entry. The massive deployement of UNO packages is not an issue.
Laurent
-- Laurent Godard <[EMAIL PROTECTED]> - Ingénierie OpenOffice.org Indesko >> http://www.indesko.com Nuxeo CPS >> http://www.nuxeo.com - http://www.cps-project.org Livre "Programmation OpenOffice.org", Eyrolles 2004
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
