Updates on packages

Wolodja Wentland debian at babilen5.org
Tue Aug 6 09:49:14 UTC 2013

On Tue, Aug 06, 2013 at 19:22 +1000, Eugenio Cano-Manuel Mendoza wrote:

> I also changed hypirion-io-clojure to io-clojure as mentioned in another thread
> (the repo has also been changed to io-clojure). Also the following jar files
> have been renamed:

I am not happy with this. The name of the upstream project is
"com.hypirion.io" and this is what we should use. If you really don't like the
"com" in there we could name the source package hypirion-io-clojure which is
in line with our naming conventions. But then I don't really have a problem
with com-hypirion-io-clojure as the name for the source package.

> hypyrion-io.jar -> io.jar

The *jar* should still be io.jar as com/hypirion/io is the name with
namespace. Please discuss this with the java team though as I deem it less
then optimal (it's such a generic name without the namespace) and it would be
good to reach a project wide conclusion. I wouldn't be too surprised if this
had been discussed before, but I couldn't find anything with a (very) quick

> The approach is just to use whatever name is supposed to have as long as it's
> not taken already. If this is not correct let me know before I change
> lein_makepkg to do this by default.

Yes, we should simply use whatever name is used by upstream, but see above and
discuss this naming strategy with the java team as the stripping of namespaces
will eventually cause problems here. I also don't really like the
FIFO approach to naming :)

> I hope this is more in line with what has been discussed if not please let me
> know, I might have misunderstood the message.

To make it clear:

UPSTREAMNAME:                   whatever is used by upstream with s/./-/
                                and other suitable transformations.


Name of the source package:     Upstream name suffixed with -clojure

Name of a library binary package:   SOURCE name prefixed with "lib"


For applications we probably want other naming rules (e.g. "leiningen" as
source and binary package name) as they are, in contrast to libraries, not
*really* associated with the language but somewhat independent. But this is
something we could discuss once we package actual applications written in

I really don't want to have more applications that are horribly named like
some shipped by pkg-perl (the entire libapp-*-perl set).
Wolodja <debian at babilen5.org>

081C B7CD FF04 2BA9 94EA  36B2 8B7F 7D30 CAF1 4EFC
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-clojure-maintainers/attachments/20130806/9d00d3ac/attachment.sig>

More information about the Pkg-clojure-maintainers mailing list