Re: Clojure team or maintainence within pkg-java?
Tom Marble <tmarble@info9.net> writes:
> My personal opinion is that it's too early to spin up a new
> team and all the associated infrastructure. Let's work on
> a design plan and implement the packaging first... It may
> become clear after this that a new team is indeed justified --
> esp. to handle bug triage.
Sounds good to me. My only reservation is I'm only interested in a small
subset of the traffic on the pkg-java team, but I think that can be
solved with mail filters.
> What would be ideal, I think, is to capture the metadata
> in Clojure libraries and use it to metadata for Clojure Debian
> packages... taking as much inspiration -- and code -- from
> leiningen as possible. If we use leiningen directly we'll
> probably have to disable live Internet downloading at build
> time (as was done with maven) as this is against Debian policy.
In the long run, once we start seeing various applications written in
Clojure that end-users would be interested in using, we will need to
repackage up lots of Clojure libraries as .debs as you suggest. But
right now the only people who are interested in using Clojure on Debian
are Clojure developers. It only makes sense to start with developer
tools. We only have two people who have expressed interest in helping,
and even that has only been focused on the relatively small task of
getting Leiningen and its four dependencies into the repositories, so
let's not over-extend our reach with premature packaging.
-Phil
Reply to: