* Francois Tigeot <ftig...@wolfpond.org> schrieb: > There are all sorts of solutions: > > - using the vendor framework (if they still care/are alive) > - installation by hand (configure / make / make install) > - lightweight management with tools such as stow: > > http://unmaintainable.wordpress.com/2007/01/14/package-management-using-stow/ > - using a third-party framework. Two of them come to mind: > - OpenPKG http://www.openpkg.org/ > - pkgsrc http://www.netbsd.org/docs/software/packages.html#platforms > > IMHO, there's no reason to include old versions of third-party packages in > LibreOffice proper.
ACK, couldn't aggree more. A few years ago (when I still did a lot of operating), I used my own buildsystem (called Briegel, ICAC) to build micro-distros ontop of existing systems (specially adapted to the individual target). Lack of proper package management on certain old cruft systems is not an legitimate reason to carry around old cruft 3rdparty packages in application's sourcetrees ;-p > In addition to all the included junk, I remember OpenOffice needing a > special-purpose version of gcc to be compiled. Yep, that was the biggest insanity I've ever seen in opensource world. (yes, in certain commercial/inhouse environments that's not so unusual, just having that in a current project ;-o) > Should we go the same path again ? Never ever, IMHO. cu -- ---------------------------------------------------------------------- Enrico Weigelt, metux IT service -- http://www.metux.de/ phone: +49 36207 519931 email: weig...@metux.de mobile: +49 151 27565287 icq: 210169427 skype: nekrad666 ---------------------------------------------------------------------- Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme ---------------------------------------------------------------------- _______________________________________________ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice