> Only spadmin is not necessary, and can be bumped. Of course, it can be > packaged after (with fondu, for example ;-) ) ? How is spadmin connected with the installer?
For Apple font install. *Always* asked. Apple font are not in the same format than Linux, as example. They have to be extracted to recover the "OOo usable form". On Mac OSX, a lot of fonts exist.
This part is not obligatory.
> So, important thing to understand is what we want to do : where Sun's > work stop, and for example where project's work begin.
How is Sun connected with this? We are *always* talking about OpenOffice.org project.
Yes, my mistake, I wanted to write OpenOffice.org, of course.
> 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...)
Yes, we do not have problem :-(
It's important.
The only problem is that we will re-invent the wheel now, tomorrow etc.
That's not my intention, but we have not a lot of time to deliver something "usable". Of course, better solution will be found after.
And, BTW, what is the frequency of official builds ? IMHO, for devel versions, we don't need to package. So only stable versions builds with installer can be another solution, and save a lot of time.
If
new builder comes, we have to teach him to produce builds *with*
installer. This is really crazy.
No, to create usable package, the build process has to be modified.
Please do not think only about yourself.
??
Thank you very much
--
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]
