Le Lundi 26 Juin 2006 15:47, Kay Ramme - Sun Germany - Hamburg a écrit : > > - OOo should not attempt to build its own packages, at least under Linux. > > Under Linux, that's the distributions' work! > > This problem is related to the "make install" one. > > In my opinion, OOo is showing the right approach here, it is IMHO > unfortunate and a waste of time, that everybody patches and builds > everything by its own, leading to small incompatibilities and bugs here > and there ...
Okay, we have diverging opinions on this point ;-). 1) I think it just makes the life of OOo package maintainers in the Linux distributions much harder. I suppose that they basically rpm-install the OOo packages, and then repackage them. Or some might have come with the idea of short-circuiting the build process just before the packages are made and then simulate a "make install". Any package maintainer listening here to confirm or denegate what I am saying ? I used to work in a linux distribution, so I think I can express opinions on this topic, but some package maintainers might see that differently. 2) What about the distros that are not "officially supported"? Debian, Slackware, ... 3) For us developpers, when we rebuild everything, it is really boring to wait until packages are built and then install them. Also, when we do only local changes, guessing the correct "cp" instruction to install our software in OOo runtime tree is much harder than running a "make install". I think it's not the role of the software developpers to distribute the software, just like it's not the role of package maintainers to develop software. If they patch the code, normally they should contribute their patches back in IssueZilla. -- Si on ne peut pas toujours compter sur ses amis, on peut toujours compter son or. (Donjon de Naheulbeuk) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
