Kevin B. Hendricks wrote:
Hi,
You could create a new project module that builds only for MacOSX and
have it deliver the new soffice script, and the Applescripts (like
Start_OOorg and OOoAdmin) to the solver by packagemaker so that they are
part of the standard OOo package for OOo. This project could also
deliver the Installer_resources directory (prebuilt). Then all epm
really does on MacOSX is simply run packagemaker with command line
options instead of interactively. So we will need to modify the command
line options to use our Installer_resources file.
We have also been given special permission by CocoaDialog's author to
use it for OpenOffice.org (even given it is GPL) so it could be housed
in a MacOSX specific directory as well (but we will need Sun/OOo to pass
that through Sun legal).
ok, I will take care of this part, if somebody can give me a pointer to
the sources I will proceed ASAP.
Then epm could be used in a slightly modified form (passing more command
line options to use our prebuilt Install_resources directory) and it
should be able to create a usable package.
That was what I planned to do anyway for the OOo 1.1.X tree once I
finally got some more free time.
If the CocoaAuthor's permission is not enough we can probably find a
replacement for it someplace that. Also I think Terry once said that he
would be happy for us to package up his official OpenOffice scripts into
OOo but please doublecheck with him.
sounds fine for me,
Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
