Mailinglist Archive: opensuse-project (168 mails)
| < Previous | Next > |
Re: [opensuse-project] Including or not Java binaries in OBS
- From: Guido Berhoerster <gber@xxxxxxxxxxxx>
- Date: Fri, 20 Apr 2012 13:25:37 +0200
- Message-id: <20120420112537.GB2723@hal>
* Johannes Weberhofer <jweberhofer@xxxxxxxxxxxxx> [2012-04-20 13:13]:
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?
--
Guido Berhoerster
--
To unsubscribe, e-mail: opensuse-project+unsubscribe@xxxxxxxxxxxx
To contact the owner, email: opensuse-project+owner@xxxxxxxxxxxx
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?
--
Guido Berhoerster
--
To unsubscribe, e-mail: opensuse-project+unsubscribe@xxxxxxxxxxxx
To contact the owner, email: opensuse-project+owner@xxxxxxxxxxxx
| < Previous | Next > |