Hi Oliver,
Thanks for your response
However, for optional packages, it should be possible to add support for
running unopkg in some postinstall process/script (I believe currently
there is none). There is also the option to just provide a skeleton for
native packaging - without further OOo integration.
the easiest way, IMHO, would be to register user-level extensions when
first starting OOo for this user at licence egreement
But the problem is for shared packages (the most used cases in fact)
Another option would be to develop a script that transfers a UNO package
into a structure that does not need unopkg calls and run it during the
packaging process, but this would basically mean it is no longer an
extension ;-).
Agree
But i think that the "distrib/packager" specific issues have to be
handled by them
If they want to add an extension, then lets split
we can perharps provide some tools to help them
but should not be our default use
OOo has a great and promising package framework
OOo is multiplateform and can not endorse sepcific deployers problems
Obviously, i'm opened to discussions :-)
My concern is to make things easy to enrich OOo
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]
