Re: RFP 702564: graphtea -- software framework to work on graphs
- To: debian-java@lists.debian.org
- Cc: Mohammad Ali Rostami <rostamiev@gmail.com>
- Subject: Re: RFP 702564: graphtea -- software framework to work on graphs
- From: Adrian Knoth <adi@drcomp.erfurt.thur.de>
- Date: Wed, 24 Apr 2013 01:15:21 +0200
- Message-id: <[🔎] 51771609.4060302@drcomp.erfurt.thur.de>
- In-reply-to: <51551DFD.8050206@debian.org>
- References: <5139F462.9080407@drcomp.erfurt.thur.de> <51521B22.4080305@drcomp.erfurt.thur.de> <CAAhs43bkSs9W2tXyPdiEuoo5FNmzCnOYSB_GqjB+ecKFYmc2ew@mail.gmail.com> <5153CC21.5020109@debian.org> <CAAhs43a_JY63RPGtOH-qKOghL+ymKV1BTawvna0goKUPP+ppxw@mail.gmail.com> <51551DFD.8050206@debian.org>
On 03/29/2013 05:52 AM, tony mancill wrote:
>> No, we do not use that library,
>> we use this library: https://code.google.com/p/jgoogleanalyticstracker/.
> I have filed an RFP bug [1] for a JGoogleAnalyticsTracker package.
> [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704186
Ali has recently dropped the JGoogleAnalyticsTracker requirement from
his upstream project.
I've created a first working Debian package:
https://github.com/adiknoth/GraphTea/tree/debian
It's based on my dfsg-upstream branch which is supposed to resemble the
future orig.tar.gz (repacked to exclude *.jar and binary/).
I've submitted most of the necessary upstream changes to upstream in a
pull request:
https://github.com/graphtheorysoftware/GraphTea/pull/23
Since they're all unintrusive, I except Ali to merge them back to
master.
As a bit of a warning: I have absolutely no Java experience at all, this
was the first time I ever compiled a Java program and wrote some lines,
so I'm not sure if I got everything right, especially wrt CLASSPATH.
Anyway, I can run
$ fakeroot debian/rules binary
in the debian branch and get a lovely graphtea_1.0-1_all.deb which
allows me to run graphtea from any directory (this wasn't possible
before, upstream always cd'ed into its distdir).
Cheers
PS: Until sufficiently mature, I'll rebase the debian/ branch whenever
necessary, so don't expect stable commit IDs.
Reply to: