Ainsi parlait Andrus Adamchik : [..] > Task of a package creator is harder. (Here is a link with detailed > information : http://www.rpm.org/max-rpm/ ). In short (in reality it is > rather hard) package creators need to get sources, convert > "configure-make-make install" into a special RPM spec for a target > platform, build it into RPM. <ignomious self-publicity> And also keep track of dependency developpers didn't explicitly provided, discard binary files and look for sources everywhere on the net, find a global coherency among hundreds of different practices, adapt to platform-specific standards, deal with license nightmare, cope with crazy archive formats, etc...
Curiously in java world, packager work is generaly is at best misunderstood, often ignored, or even seen with some hostility from developpers. But the result is here: jpackage project covers today more than a hundred of different java projects. See http://jpackage.sourceforge.net for complete list. </ignomious self-publicity> -- Guillaume Rousse <[EMAIL PROTECTED]> GPG key http://lis.snv.jussieu.fr/~rousse/gpgkey.html -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
