Re: Re: [releases] Mac OS X port and 2.0beta2

Hi,

Martin Hollmichel a écrit :
>> My arguments are simple:
>> - a launcher is absolutly necessary (else OOo won't be used by Mac Users)
>> - we have a usable GPL solution
>> - with a native port, this launcher won't be necessary
>>
> It looks like we want to use an existing one ?

Yes, and working fine.

> It there any code to OpenOffice.org source code, meaning problems with 
> calls from GPL to LGPL code ?

I don't think so, but because licenses problem are sometimes a bit 
difficult for me, I propose to explain more what exactly I  mean :

1) The entire build "dmake ..." is done without any change : ~20 
packages .pkg are created at the end

2) Packaging is modified. Let's call it extra-packaging (only Mac OS X 
is concerned):

Only one .dmg is created, replacing the ~ 20 in classical build process, 
and this can be done manually first by the builder, for tests. Later, a 
script could be used to improve the process, because of the number of 
concerned locales.

I ask to integrate the launcher in extra-packaging process (including 
launcher's build). This part includes :
- compile Applescript  : can probably be made from command-line, so its 
interesting for us
- compile the entire launcher application : all the stuff could be 
include in an "XCode tree like" and be built from command line

-> the result is a folder containing binary + all stuff needed, and is 
called "bundle"

- create metapackage (transform ~20 .pkg in one only )
- create .dmg : archive containing everything.


Note : what means " a launcher " -> this is an application written in 
Applescript, with all the needed stuff around to make it graphical 
(icon, definition files, translation files etc). Around 1Mo is needed here.

To make short : launcher means *just* execute soffice script, after have 
correctly sourced the environment.
IMHO, they're no internal calls for any binary, just a layout with the 
sytem (using another API).


My question is :

Is it possible to include all this stuff actually exisitng, but under 
GPL, in the sources  ? For now, "where" is undefined).
This way, we could obtain a complete autoinstallable package, with 
expected feature : dockable launcher.

Of course, if ever this is possible, we need to know the exact origin of 
every file in this part.

I'm not sure to be clear, so feel free to ask questions, and correct me 
if I'm wrong.


Regards,
eric bachard

-- 
<[email protected]>
Francophone OpenOffice.org Community developer ( Linux PPC and Mac OS X 
/ X11)
See : <http://fr.openoffice.org>