Path: csiph.com!aioe.org!bofh.it!news.nic.it!robomod From: Brad Wood Newsgroups: linux.debian.bugs.dist,linux.debian.maint.java Subject: Bug#792018: RFS: commandbox/2.0.0 ITP -- CFML REPL, CLI, Package Manager, and Embedded Server Date: Wed, 22 Jul 2015 07:50:01 +0200 Message-ID: References: X-Original-To: Emmanuel Bourg Old-Return-Path: X-Spam-Flag: NO X-Spam-Score: -3.786 Reply-To: Brad Wood , 792018@bugs.debian.org Resent-To: debian-bugs-dist@lists.debian.org Resent-Cc: wnpp@debian.org, Brad Wood X-Debian-Pr-Message: followup 792018 X-Debian-Pr-Package: wnpp X-Spam-Bayes: score:0.0000 Tokens: new, 12; hammy, 150; neutral, 193; spammy, 0. spammytokens: hammytokens:0.000-+--UD:anonscm.debian.org, 0.000-+--sk:anonscm, 0.000-+--anonscmdebianorg, 0.000-+--anonscm.debian.org, 0.000-+--debuild Dkim-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=9NoVWv7zAvfKTEND8WuutSdbzI4KYzBh8hMBgwGN8Ko=; b=H8WNectZ5lEpAvdjlL3sWmioi2aeE1oGlRmKUqPvtiIh/WaY+aLobtmpyGTATou5fp 8O/wIXIDww28Pa0BGXK5keD5yxKW0pqS66gFD4zlqMgCX8FPmsWaSQY4OvGJybdO4MDb hUx27UQd0gpOORsIfq0/vYLZtiY3xZJz9Y6lPSLCSwe7AjS4iQUVUuH5lIGK4Jr74+ur BhJZMUYNeYYs3zxr5LPjJ2whIOAmQp+t8DWUppKcYS/8GkpOuDhsVcqBXrhlD4E/dItA 2e8P9W2Ow7VrADduevA71O5BLm9N2WAeUAQOS8GckkWfghB4tc/K2iMaWbd21xMQqiyM h2Fg== X-Received: by 10.202.178.212 with SMTP id b203mr658945oif.0.1437543694969; Tue, 21 Jul 2015 22:41:34 -0700 (PDT) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary=001a113b5ebc49b1f9051b7039d3 X-Debian-Message: from BTS X-Mailing-List: archive/latest/1192775 List-ID: List-URL: Approved: robomod@news.nic.it Lines: 178 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: 792018@bugs.debian.org, Brad Wood , debian-java@lists.debian.org X-Original-Date: Wed, 22 Jul 2015 00:41:15 -0500 X-Original-Message-ID: X-Original-References: <55A76F1F.1000006@apache.org> <55AB8C12.6000301@apache.org> Xref: aioe.org linux.debian.bugs.dist:666210 linux.debian.maint.java:8200 --001a113b5ebc49b1f9051b7039d3 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Thanks again for the answers Emmanuel. Due to the large amount of work that will be involved in packaging every Java dependency, we'll probably table this effort for now and come back to it at a later date. Thanks! ~Brad *ColdBox Platform Evangelist* *Ortus Solutions, Corp * E-mail: brad@coldbox.org ColdBox Platform: http://www.coldbox.org Blog: http://www.codersrevolution.com On Sun, Jul 19, 2015 at 6:37 AM, Emmanuel Bourg wrote: > Le 18/07/2015 08:18, Brad Wood a =C3=A9crit : > > > A source package makes sense in theory, but how do I create it? Does it > > contain the uncompiled Java and CFML source for the project? If the > > source package must contain everything necessary to build my project, > > what restrictions are their on the build tools? Will I have to rewrite > > to something other than Ant? The current build is rather large and > > includes generation of API docs, and updating our artifacts repo. > > A source package consists in the uncompiled upstream sources plus Debian > specific metadata and a makefile to build the project. Usually this > makefile delegates the work to the upstream build system, so you don't > have to rewrite something from scratch. > > See for example the jsch package [1]. It contains the upstream sources > and an additional 'debian' directory. In this directory you'll find the > control file [2] that specifies the name, the description and the > dependencies of the source and binary packages, and the rules makefile > [3] that invokes the upstream Ant build file and assembles the jar files > and documentation produced into the final binary packages. The control > directory contains other files used by the makefile to build the binary > package. > > If you clone the jsch package repository you can build the source and > the binary package with the 'debuild' command (you have to install the > devscripts package first). > > > > Does this mean I'd have to go through this entire process for every 3rd > > party lib and get them as separate packages on the Debian repo? Can I > > solicit sponsorship for packages I don't have any control over? How do > > you handle different versions of jars? For instance, my project may > > need version 2.1 even though 2.3 is the latest, etc. Does that also > > mean I'd have to create a source package and figure out how to compile > > each of the 3rd party libraries? > > You are correct, every dependency must be packaged separately, and you > can package them even if you aren't an upstream developer (and we'll > happily support you in the process). If an already packaged dependency > is incompatible with your project, you can either patch your code to > work with the version available in Debian, or create a duplicate package > with a fixed version for this dependency (this isn't the common case > fortunately). > > Emmanuel Bourg > > [1] http://anonscm.debian.org/cgit/pkg-java/jsch.git/tree/ > [2] http://anonscm.debian.org/cgit/pkg-java/jsch.git/tree/debian/control > [3] http://anonscm.debian.org/cgit/pkg-java/jsch.git/tree/debian/rules > > --001a113b5ebc49b1f9051b7039d3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Thanks again for the answers Emmanuel.=C2=A0 Due to the la= rge amount of work that will be involved in packaging every Java dependency= , we'll probably table this effort for now and come back to it at a lat= er date.

Thanks!
~Brad

ColdBox Platform Evangelist
Ortus Solutions, Corp=C2=A0

=
ColdBox Platform: http://www.coldbox.org=C2=A0


On Sun, Jul 19, 2015 at 6:37 AM, Emmanuel Bo= urg <ebourg@apache.org> wrote:
Le 18/07/2015 08:18, Brad Wood a =C3=A9crit :

> A source package makes sense in theory, but how do I create it? Does i= t
> contain the uncompiled Java and CFML source for the project?=C2=A0 If = the
> source package must contain everything necessary to build my project,<= br> > what restrictions are their on the build tools?=C2=A0 Will I have to r= ewrite
> to something other than Ant?=C2=A0 The current build is rather large a= nd
> includes generation of API docs, and updating our artifacts repo.

A source package consists in the uncompiled upstream sources plus De= bian
specific metadata and a makefile to build the project. Usually this
makefile delegates the work to the upstream build system, so you don't<= br> have to rewrite something from scratch.

See for example the jsch package [1]. It contains the upstream sources
and an additional 'debian' directory. In this directory you'll = find the
control file [2] that specifies the name, the description and the
dependencies of the source and binary packages, and the rules makefile
[3] that invokes the upstream Ant build file and assembles the jar files and documentation produced into the final binary packages. The control
directory contains other files used by the makefile to build the binary
package.

If you clone the jsch package repository you can build the source and
the binary package with the 'debuild' command (you have to install = the
devscripts package first).


> Does this mean I'd have to go through this entire process for ever= y 3rd
> party lib and get them as separate packages on the Debian repo?=C2=A0 = Can I
> solicit sponsorship for packages I don't have any control over?=C2= =A0 How do
> you handle different versions of jars?=C2=A0 For instance, my project = may
> need version 2.1 even though 2.3 is the latest, etc.=C2=A0 Does that a= lso
> mean I'd have to create a source package and figure out how to com= pile
> each of the 3rd party libraries?

You are correct, every dependency must be packaged separately, and y= ou
can package them even if you aren't an upstream developer (and we'l= l
happily support you in the process). If an already packaged dependency
is incompatible with your project, you can either patch your code to
work with the version available in Debian, or create a duplicate package with a fixed version for this dependency (this isn't the common case fortunately).

Emmanuel Bourg

[1] http://anonscm.debian.org/cgit/pkg-java/j= sch.git/tree/
[2] http://anonscm.debian.org/cg= it/pkg-java/jsch.git/tree/debian/control
[3] http://anonscm.debian.org/cgit= /pkg-java/jsch.git/tree/debian/rules


--001a113b5ebc49b1f9051b7039d3-- -- To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org