Hi Martin, On Monday 15 October 2007 14:11, Martin Hollmichel wrote:
> > But for the Win32 builders, searching for the dependencies > > could be too expensive - that's why I propose the 'super-source-package' > > ;-) Of course, we can go the way of ooo-3rdparty-dictionaries, > > ooo-3rdparty-epm, ooo-3rdparty-hsqldb, etc. but I'm not sure if it helps > > in the end... > > this was what I was thinking about, just redistributing the 3rdparty > packages as single one to achive maximum modularity at that level. But the maximum modularity is achieved if the developers use the versions from their distros. I understand ooo-libs-3rdparty as a fallback for the developers that don't want to install the pieces; the ./configure would detect if there are 'system' versions of this or that, and build just the pieces that are not there. > If we > target the Windows developer I'd vote for a one click download again > (one really super tarball), otherwise people will go into an several > hour lasting "configure - missing dependency - download" circle. Well, considering that the binary compatibility of ooo-libs-3rdparty changes ~once in a year, I think it is worth having split even in the Win32 case. Regards, Jan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
