[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#736123: ITP: sbbi-upnplib -- Java library for universal plug and play (upnp)



Hi,

Most java library source packages don't respect the format libXXX-java, which is rather meant for the binary package.

Keeping the upstream name for the source and, as noted by Jonathan, considering the fact that one source might create more than a library, e.g. a javadoc package, that sounds right to me.

Eric

Jonathan Yu <jawnsy@cpan.org> wrote:
Hey Scott,

It has been said that "There are only two hard things in Computer
Science: cache invalidation and naming things." -- Phil Karlton :-)

The binary package was of the most concern to me, because that's what
users will look for when installing. I actually have no experience
with Java packaging, so I'm not sure what the conventions are there.
Personally, my preference would be for source + binary packages to be
the same name.

I used to work on packaging Perl libraries mainly, and in that case,
our convention was generally to stick with the lib*-perl pattern, for
both source and binary packages. Initially, we also did this for
applications (e.g. libcpanminus-perl), but later decided to go with
just application names (i.e. cpanminus) in cases where the application
is meant to be used standalone and not as a library. We codified these
conventions in the policy for th e Debian Perl Group [0]. Whether
something is more appropriately a library or application requires some
discretion on the part of the packaging Debian contributor/developer,
of course. And I'm not sure what to name the source package in a case
where there is both a library and application component. I guess the
analogue with Perl modules is also different because upstream Perl
package names (Module::Name) are not valid Debian package names
anyway, so they have to be transmogrified to fit our convention, and
lib*-perl seems as fine a convention as any.

Does apt-get source expect the source package name, or will it also
work with binary package names? If I do "apt-get source libupnp-java",
will it download the sbbi-upnplib package? If so, then this seems to
be an especially trivial point, and I'd be happy with either name. In
any case, since I'm not an expert here, let's see if someone on the
debian-java list chimes in :-)

Cheers,

Jonathan

[0] http://pkg-perl.alioth.debian.org/policy.html#package_naming_policy

On Sun, Jan 19, 2014 at 9:43 PM, Scott Howard <showard314@gmail.com> wrote:
Hi all,
The binary package is named libupnp-java, seen here:
http://anonscm.debian.org/gitweb/?p=pkg-java/sbbi-upnplib.git;a=blob;f=debian/control;h=8014fb5b4d2c3eb60968caaa6c239562002dd9f7;hb=HEAD

I named the source package to match the name of the upstream tarball
file (sbbi-upnplib-1.0.4.tar.gz) I struggled with either naming the
source package the same as the bi nary package, or to name it like I
suggest here. Since upstream refers to the project as sbbi-upnplib and
their tarball had that in it, I'm leaning toward keeping the name what
they call it. It will be discoverable since the binary package has the
proper java library package name. I was worried about it not being
discoverable if I didn't put the sbbi-upnplib source package name.

Given that, do you still think it should be renamed? I don't mind either way.

~Scott

On Sun, Jan 19, 2014 at 8:50 PM, Jonathan Yu <jawnsy@cpan.org> wrote:
Hey Scott,

I don't presume to be an expert here, but I wanted to mention that the
package name specified in your ITP does not match the usual
conventions for libraries in Debian, nor for Java libraries
specifically:

"Jav a libraries packages must be named libXXX[version]-java (without
the brackets)" [0]

Might you consider renaming this package to make it more easily discoverable?

Cheers,

Jonathan

[0] http://www.debian.org/doc/packaging-manuals/java-policy/x104.html

On Sun, Jan 19, 2014 at 5:33 PM, Scott Howard <showard@debian.org> wrote:
Package: wnpp
Severity: wishlist
Owner: Scott Howard <showard@debian.org>

* Package name : sbbi-upnplib
Version : 1.0.4
Upstream Author : SuperBonBon Industries
* URL : http://sourceforge.net/p/triplea/code/HEAD/tree/upnp/
* License : Apache-1.1
Programming Lang: Java
Description : Java library for universal plug and play (upnp)

This is a dependency of the newest versions of the triplea package. To be
maintained under the java team umbrella.
Initial repo:
http://anonscm.debian.org/gitweb/?p=pkg-java/sbbi-upnplib.git


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: [🔎] 20140119223359.15198.7602.reportbug@esc-303123.ee.nd.edu">http://lists.debian.org/[🔎] 20140119223359.15198.7602.reportbug@esc-303123.ee.nd.edu



--
To UNSUBSCRIBE, email to debian-java-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: [🔎] CAMDxSEjLKidDA__V6LFzBE+iAF0J5yOcL6uoaongOQ0rR3ZNyg@mail.gmail.com">http://lists.debian.org/[🔎] CAMDxSEjLKidDA__V6LFzBE+iAF0J5yOcL6uoaongOQ0rR3ZNyg@mail.gmail.com



I'm on debian-java, java maintainers, vdr maintainers and debian-mentors; no need to CC me on these lists. Thanks!
Reply to: