From: "eric.bachard" <[EMAIL PROTECTED]>
Date: Tue, 22 Feb 2005 19:33:24 +0100
> Pavel Janík a écrit :
> > > 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.
And is spadmin the tool to extract them? Excuse me, but I do not know MacOS
X very well, as you already know ;-)
> > > 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.
This also doesn't make sense. On GNU/Linux we produce final packages that
are to be used for the installation. Why should this be different for other
operating system?
> 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.
I think we are in the same position like we-want-NSIS-installer-for-Windows
people. You can't package only final version because:
- you have to do QA before actual release
- QA has to be done from the beginning, so the installation itself has to
be QAed
- QAing non-final packages is lost work
-> you have to produce final packages/installers regularly to get better
testing and feedback.
It is not about frequency. It is pretty independent. Does frequency of
official build matter for producing RPM packages on GNU/Linux? How is MacOS
X different from GNU/Linux?
> > 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.
Yes. Finally we 100% agree ;-) I was convinced that MacOS X users need
different installer than we produce now. This is an issue and has to be
solved. Solved like other issues: in our CVS to have it fixed in next
release, verified and FINALLY closed.
We again speak to much instead of actually doing something, sorry for that.
--
Pavel Janík
"printk(KERN_ERR "happy meal: Receiver BigMac ATTACK!");"
-- Linux kernel: drivers/net/sunhme.c
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
