FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian Java

 
 
LinkBack Thread Tools
 
Old 11-08-2010, 09:54 PM
"Damien Raude-Morvan"
 
Default Request for reviewing my first java package

Le lundi 08 novembre 2010 23:32:21, Gilles Filippini a écrit :
> Hello pkg-java team,

Hi Gilles,
[You should use debian-java@lists.debian.org to contact the team as on
http://wiki.debian.org/Teams/JavaPackaging]

[...]
> I'd be very glad if someone from the pkg-java team could have a look at
> the package and tell me in case I'm doing something wrong regarding the
> Debian policy for Java.

I think it's a wise idea. We could really improve Debian quality by doing some
peer-review of packages. Maybe I'll find some free-time to write a proposal
about that... , some day.

> This is a rather simple package and it is available from git.d.o [2].

Some comments from a quick overview :

- debian/README.source doesn't seems to contains any useful info. You might
want to drop it.

- debian/control : no need for ${shlibsepends} substvar on arch:All package
libjxgrabkey-java
=> libjxgrabkey-java won't embed any system libs and dh_shlibdeps won't
generate anything useful from it

- debian/rules seems to use directly openjdk with CPPFLAGS="-
I/usr/lib/jvm/java-6-openjdk/include" so you have to B-D on it directly
instead of default-jdk
=> some arch doesn't have openjdk has "default-jdk" but GCJ so your package
will FTBFS on those arch.

Everything else seems fine from my point of view !

Cheers,
--
Damien - Debian Developper
http://wiki.debian.org/DamienRaudeMorvan
 
Old 11-09-2010, 12:13 AM
Scott Howard
 
Default Request for reviewing my first java package

For the benefit of the Java team, I copied the original email below:

"Hello pkg-java team,

I'm in the process of packaging a Java library (JXGrabKey [1]) and will
soon upload it to unstable. But since this is my very first Java package
I'd prefer if it could first have some reviewing from a regular Java
package maintainer.

I'd be very glad if someone from the pkg-java team could have a look at
the package and tell me in case I'm doing something wrong regarding the
Debian policy for Java.

This is a rather simple package and it is available from git.d.o [2].

Many thanks in advance,

(Please CC me on replies)

_g.

[1] <http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=602836>
[2] <http://git.debian.org/?p=collab-maint/jxgrabkey.git>"



Ok, for my review (on top of Damien's helpful comments):
1) Nice work! Java packaging requires more manually tweaking to be
java policy compliant that other packages, and you did a good job
figuring out what goes where.
In the future you can consider the javahelper package (read the
javahelper tutorial in the package too). It has some nice debhelper
addons that will make installing libraries easier. (you move them
around a bit and rename/symlink them to get them to work which is
great, but is easily done automagically with javahelper). It can also
be used to link the javadoc for you too.
2) debian/docs appears to be empty (probably can just delete it)
3) the upstream changelog can be installed using
override_dh_installchangelogs: dh_installchangelogs -k
misc/ReleaseFiles/CHANGELOG.txt
instead of using mv and renaming
4) you rename the library from JXGrabKey.jar to jxgrabkey.jar. To be
compatible with other projects that may use your library, you should
keep the same capitalization. javahelper's script "jh_installlibs"
will do that for you, install it to /usr/share/java, and install the
correctly formatted versioned .jar and the symlink per policy.
5) your git repo can use tags for the upstream/pristine tar section (I
couldn't build your package using git buildpackage since there was no
upstream tags). There are some good how tos on the internet showing
how you can do that
6) Builds fine, only lintian pedantic or info is:
I: libjxgrabkey-java: extended-description-is-probably-too-short
P: libjxgrabkey-jni: no-upstream-changelog
I: libjxgrabkey-doc: extended-description-is-probably-too-short
P: libjxgrabkey-doc: no-upstream-changelog

(The upstream changelog pedantic warnings would be fixed using the
dh_installchangelogs command I mentioned above)

7) regarding the CPPFLAGS listed in debian/rules, I believe you can
drop that. It's bad to put that hard coded -I path in case an arch
doesn't have that path. That include shouldn't be necessary at all. If
you really need it, you can use
CPPFLAGS="-I/usr/lib/jvm/default-java/include" which should work on
all archs.

Great job!
Regards,
Scott


--
To UNSUBSCRIBE, email to debian-java-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: AANLkTi=hPHKLDxYG_aCCoCN1E_ibrK5P72Eezah7=LZn@mail .gmail.com">http://lists.debian.org/AANLkTi=hPHKLDxYG_aCCoCN1E_ibrK5P72Eezah7=LZn@mail .gmail.com
 
Old 11-09-2010, 11:16 PM
Gilles Filippini
 
Default Request for reviewing my first java package

Hi,

Damien Raude-Morvan a écrit , Le 08/11/2010 23:54:
> Le lundi 08 novembre 2010 23:32:21, Gilles Filippini a écrit :
>> Hello pkg-java team,
>
> Hi Gilles,
> [You should use debian-java@lists.debian.org to contact the team as on
> http://wiki.debian.org/Teams/JavaPackaging]

Sorry about that. I missed to check the team's wiki page.

> - debian/README.source doesn't seems to contains any useful info. You might
> want to drop it.

Oops. Sure

> - debian/control : no need for ${shlibsepends} substvar on arch:All package
> libjxgrabkey-java
> => libjxgrabkey-java won't embed any system libs and dh_shlibdeps won't
> generate anything useful from it

Fixed.

> - debian/rules seems to use directly openjdk with CPPFLAGS="-
> I/usr/lib/jvm/java-6-openjdk/include" so you have to B-D on it directly
> instead of default-jdk
> => some arch doesn't have openjdk has "default-jdk" but GCJ so your package
> will FTBFS on those arch.

CPPFLAGS isn't needed anymore. I've dropped this setting.

Scott Howard a écrit , Le 09/11/2010 02:13:
> In the future you can consider the javahelper package (read the
> javahelper tutorial in the package too). It has some nice debhelper
> addons that will make installing libraries easier. (you move them
> around a bit and rename/symlink them to get them to work which is
> great, but is easily done automagically with javahelper). It can also
> be used to link the javadoc for you too.

I didn't know about javahelper. It is indeed convenient for the simlink
handling. But I won't use it for the javadoc part because I'm not happy
with the resulting doc-base file.

> 2) debian/docs appears to be empty (probably can just delete it)

Fixed.

> 3) the upstream changelog can be installed using
> override_dh_installchangelogs: dh_installchangelogs -k
> misc/ReleaseFiles/CHANGELOG.txt
> instead of using mv and renaming

Fixed.

> 4) you rename the library from JXGrabKey.jar to jxgrabkey.jar. To be
> compatible with other projects that may use your library, you should
> keep the same capitalization. javahelper's script "jh_installlibs"
> will do that for you, install it to /usr/share/java, and install the
> correctly formatted versioned .jar and the symlink per policy.

Fixed using jh_installlibs.

> 5) your git repo can use tags for the upstream/pristine tar section (I
> couldn't build your package using git buildpackage since there was no
> upstream tags). There are some good how tos on the internet showing
> how you can do that

Fixed. This was a side effect of not using git-import-orig for the first
release of the package :/

> 6) Builds fine, only lintian pedantic or info is:
> I: libjxgrabkey-java: extended-description-is-probably-too-short
> P: libjxgrabkey-jni: no-upstream-changelog
> I: libjxgrabkey-doc: extended-description-is-probably-too-short
> P: libjxgrabkey-doc: no-upstream-changelog
>
> (The upstream changelog pedantic warnings would be fixed using the
> dh_installchangelogs command I mentioned above)

Fixed thanks to dh_installchangelogs.

> 7) regarding the CPPFLAGS listed in debian/rules, I believe you can
> drop that. It's bad to put that hard coded -I path in case an arch
> doesn't have that path. That include shouldn't be necessary at all. If
> you really need it, you can use
> CPPFLAGS="-I/usr/lib/jvm/default-java/include" which should work on
> all archs.

It does work indeed.
Anyway it seems debian/rules doesn't need this setting anymore. Must
have been a side effect of previous attempts.


Many thanks for these reviews. They are highly appreciated.

_g.
 

Thread Tools




All times are GMT. The time now is 01:45 AM.

VBulletin, Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright ©2007 - 2008, www.linux-archive.org