Hi Pavel,

Pavel Janík a écrit :
   From: "eric.bachard" <[EMAIL PROTECTED]>
   Date: Mon, 21 Feb 2005 12:57:15 +0100

   > Note : This installer is under GPL licence

This means it can be committed to CVS -> there is no way it can be the
default installer for OOo on MacOS X.

Yes Pavel, you're right : LGPL license strikes again...

I think it is important to do an inventory of what is needed, what we can do and what we cannot, with the installer I propose.

Let me begin to analyse :

- actual packaging -means the one you produce, mine is other thing- gives ".pkg" *it is* OOo, and can be Sun produced even if actually automated build isn't IMHO possible yet (I'm actually building m80 with a lot of breaks ).
Important : to be honest, the Mac Users won't use such packages. You can believe me :-)


Mac Users just want to click and drag'N drop. If not, they simply won't use your software. That's all. It's not what we want...right ?


Now, what is "external" :

- external stuff : XCode (Apple software, including packagemaker), CocoaDialog (I have the sources,and this part is under GPL. Author is Mark A. Stratman <[EMAIL PROTECTED]> , StartOOo made by Terry Teague (*please confirm* ) and includes Sun parts.

Only spadmin is not necessary, and can be bumped. Of course, it can be packaged after (with fondu, for example ;-) )

- these files have to be modified (useless functionnalities have to be cleaned up), pathes are different, some tests are to do too...

- manual packaging is needed : one per locale. This includes : create a directory containing 2 directories (Install_resources and Packages) + pre/post install scripts and some fully customizable things. And build


That's all


IMHO, the packaging is completely a third part piece. Nothing of the content is modified by the installer I proposed. Just the package changes. *It's essential*.


So, important thing to understand is what we want to do : where Sun's work stop, and for example where project's work begin.


Last but not least. If no compromised is found, is it correct to package OOo with what I proposed above, *without* break LGPL ? If so I don't see a problem...)


Can someone confirm, please ?


Regards, eric bachard



--
eric bachard <[EMAIL PROTECTED]>
French OpenOffice.org Community contributor (build of french releases for Linux PPC and Mac OS X / X11)
See : <http://fr.openoffice.org>


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to