Mailinglist Archive: opensuse-java (8 mails)
| < Previous | Next > |
Re: [opensuse-java] jMemorize, XLogo and GeoGebra status update
- From: Michal Vyskocil <mvyskocil@xxxxxxx>
- Date: Wed, 18 Jun 2008 16:16:26 +0200
- Message-id: <200806181616.26542.mvyskocil@xxxxxxx>
On Sunday 08 June 2008 23:07:42 Kirill Kirillov wrote:
Hi,
great work!
Well, the openSUSE has support for binfmt_misc, so it's possible to run
the jar as elf binary - chmod a+x foo.jar, ./foo.jar works. But the
common way is to use some shell script to in /usr/bin, than executable
jar, because this shoule work on every Unix system.
As I see, you've modify a source tarball directly. Please do not modify
an upstream tarball directly, this is bad for maintenace. The better
solution is use a patch, add him to the spec, because it's clear what
is an upstream code and what is a vendor's change.
Spec:
Patch0: %{name}-remove-signjar.patch
%patch0 -b .sav
There's something informations about %patch macro
http://www.rpm.org/max-rpm/s1-rpm-inside-macros.html
and a patching
http://www.ibm.com/developerworks/library/l-rpm2/
I'll contact adrian and get some result from him. There's some support
for gpg signing, so it may be easy to add somethink for java packages.
MV
--
To unsubscribe, e-mail: opensuse-java+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-java+help@xxxxxxxxxxxx
Hello all.
Hi,
great work!
1) I've improved jMemorize.spec [1] according to java guidelines, so
it can be included to Factory. I've question about it: please explain
what permissions should jar files have: 0755 or 0644?
Well, the openSUSE has support for binfmt_misc, so it's possible to run
the jar as elf binary - chmod a+x foo.jar, ./foo.jar works. But the
common way is to use some shell script to in /usr/bin, than executable
jar, because this shoule work on every Unix system.
2) I've built XLogo from source codes [2]. I've question about
signing jar files: is it possible to sign jar in BuildService? For
now signing is disabled (correspondent lines removed from build.xml),
so final xlogo.jar is not suitable for using in Java Web Start in
websites, so it's only for local use.
As I see, you've modify a source tarball directly. Please do not modify
an upstream tarball directly, this is bad for maintenace. The better
solution is use a patch, add him to the spec, because it's clear what
is an upstream code and what is a vendor's change.
Spec:
Patch0: %{name}-remove-signjar.patch
%patch0 -b .sav
There's something informations about %patch macro
http://www.rpm.org/max-rpm/s1-rpm-inside-macros.html
and a patching
http://www.ibm.com/developerworks/library/l-rpm2/
3) I've asked GeoGebra developers about migrating to BuildService for
providing rpm, but GeoGebra has build-in feature to export the
construction as a webpage. This export includes the GeoGebra applet
which should be signed and GeoGebra developers are trying to avoid
appearing unsigned jars on the web. Is it possible to resolve this
problem?
I'll contact adrian and get some result from him. There's some support
for gpg signing, so it may be easy to add somethink for java packages.
MV
--
To unsubscribe, e-mail: opensuse-java+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-java+help@xxxxxxxxxxxx
| < Previous | Next > |