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? Best regards, Johannes Am 20.04.12 12:58, schrieb Ludwig Nussel:
Pascal Bleser wrote:
[...] - how likely is it that we are going to patch an upstream java library or application ourselves, rather than updating it to an upstream release that fixes the issue ? * very few in this project are fluent with java * is it an issue to push a newer version to fix rather than backporting changes/patches for those packages ?
Well, just recently we had the case where a fix was only a few lines but the package couldn't be rebuilt from java source and upstream only offered a major version update. That sucks. It's embarrassing if a package is flagged as free software but you can't actually fix it. If at all exceptions should be granted only on a case by case basis after thorough review. Also such packages should not be put in the oss tree.
cu Ludwig
-- 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