[Pkg-running-devel] looking for a sponsor for my 'qtrainer' package

[Christian PERRIER]

Quoting Michael Olberg (michael.olberg at chalmers.se):
> Hi Christian,
> 
> I saw your name listed in connection with the
> garmin-forerunner-tools for debian, and I also know from your blog
> that you are a frequent runner, so I was wondering if you would be
> willing to help me get the following package into debian (or tell me
> who else I should contact):
> 
> debian/control:
> ---------------
> Source: qtrainer
> Section: universe/utils
> Priority: optional
> Maintainer: Michael Olberg <michael.olberg at chalmers.se>
> Build-Depends: debhelper (>= 7), libqt4-dev, libqwt5-qt4-dev,
> qt4-qmake, libqmapcontrol-dev
> Standards-Version: 3.8.3
> 
> Package: qtrainer
> Architecture: any
> Depends: libqmapcontrol, ${shlibs:Depends}, ${misc:Depends}
> Recommends: garmin-forerunner-tools, sqlite3
> Description: A Qt application to log and view data from Garmin
> Forerunner devices.
>  It is geared towards running, using a sqlite database to store track
>  data. Qtrainer is written in C++ using the Qt4 gui framework.
> -----------------
> 
> So far I have packaged it (for personal use only) for Ubuntu, where
> it builds lintian-cleanly. The libqmapcontrol is my packaged version
> of the freely available QMapControl Qt widget
> (http://www.medieninf.de/qmapcontrol/)
> 
> I attach a screenshot. The package is available at
> 
> deb http://nain.oso.chalmers.se/oso/ubuntu/ precise contrib
> deb-src http://nain.oso.chalmers.se/oso/ubuntu/ precise contrib

Hello Michael,

Very sorry for coming back at you very late. I didn't have time during
my holidays to look at your packages, as I originally promised.

I just had a brief look now.

Well, first of all, we need to have libqmapcontrol in Debian before we
can upload qtrainer.

However, a first look at your source package raises a quite important
concern to me. You seem to heavily patch the upstream sources. It is
fine, but this is done directly in the diff.gz file and not as patches
in debian/patches. So, it makes difficult to identify what are the
changes to upstream sources and why you made them.

In short, I heavily recommend you use source v3 format and not source
v1, with quilt patches in debian/patches.

Could you consider that?


-------------- 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-running-devel/attachments/20121028/602e193f/attachment.pgp>