Sorry, I didn't mean binary jars; a better wording would be "non-source-distribution" packages, in contrary to the source packages. Eg. Geronimo uses http://www.apache.org/dyn/closer.cgi/geronimo/2.2.1/geronimo-2.2.1-source-re... as source package and http://www.apache.org/dyn/closer.cgi/geronimo/2.2.1/geronimo-tomcat6-javaee5... as compiled/packaged installation package. For my needs, I'm packaging the second one. A great thing would be, when the OBS could run the maven tool using it's download feature! The the complete packaging process could be done in OBS very easily, but external jars would be downloaded from their maven repos. Best regards, Johannes Am 20.04.12 13:25, schrieb Guido Berhoerster:
* Johannes Weberhofer
[2012-04-20 13:13]: Some tine ago I started to package Apache Geronimo. After a few days, I'd stopped, because there are around 400 jars packaged; some sources need additional sources just for packaging/compiling. It would have taken month to build that with the resources I can spend. Currently I'm building the package from the Apache binaries and do not offer the package via the obs. It's sometimes very frustrating, because even when some of the packages have already been built for suse, the versions do not match with the required versions. I'd very much love to package binary jars for some projects. But I also understand, that it doesn't fit to the build-service philosophy. Couldn't we have a special repository, where such kind of packages are allowed?
How are binary jars different from statically linked binaries and private library copies which are rightfully outlawed. Having a package with 400 inlined jars sounds like a nightmare, are the packager or upstream closely monitoring 400 upstream projects for security issues?
-- Johannes Weberhofer Weberhofer GmbH, Austria, Vienna -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org