Just my 2 cents: as packager of a distro called openmamba (a rolling release one) I would point out that is not so trivial build an universal package of a complex software like LibO. We use RPM as package so we could use Mandriva, Suse or Red Hat RPMs but we prefer build ours: we try to use the biggest number of system library possible (not always done by other distro), we have automatic procedure to upgrade SPECS and build new RPM (there is a server that crawls the sites to search new version of software and then automatically builds out new RPMS) but to do this is important that the specfiles are formatted in a precise way, and last but not least the paths of the installation can vary from. As example some messages ago someone point out the missing of new thunderbird in ubuntu repository, we are in the same situation,and is due to some changes to libraries requested by 3.1.4, these change will broke other packages we use; on the other hand we have the rpm of the new gimp version out and ready to install the day *before* the official announce. Installing or upgrading a package not studied for the distro used can make more damages than goods, so I agree with who says that is better to don't prepare packages. Regards Ercole Carpanetto
-- To unsubscribe, e-mail to [email protected] All messages you send to this list will be publicly archived and cannot be deleted. List archives are available at http://www.documentfoundation.org/lists/discuss/
