Re: Doubts in Sigar packaging

2010-09-17 Thread Enrico Weigelt
* Tony Houghton schrieb: > If upstream aren't using tags that are or can be mangled to be sortable > and representative of some sort of release versioning then, yes, you've > got difficulties, but if they are, that plus number of commits gives you > a sortable and meaningful version string, and t

Re: RFS: flightgear, fgfs-base and simgear (updated packages) and 16 new flightgear related packages (attempt three)

2010-09-17 Thread Henrique de Moraes Holschuh
On Fri, 17 Sep 2010, Chris Baines wrote: > The main reason for the number of packages is to allow customisation. > The reasons are different for the individual packages, for instance the > scenery package is not needed if the user wants to use terrasync for > scenery and the fgfs-base-models packag

RFS: pysolfc (replacement for removed package: pysol)

2010-09-17 Thread Bernhard Reiter
Hello mentors, I am looking for a sponsor for my package "pysolfc". * Package name: pysolfc Version : 2.0-1 * URL : http://pysolfc.sourceforge.net/ * License : GPL * Programming Lang: Python * Description : A Python solitaire game collection It builds the binary package: pysol

Re: git-buildpackage and patches

2010-09-17 Thread Laurent Léonard
Le vendredi 17 septembre 2010 15:36:18, Pietro Battiston a écrit : > Hello, > > I like git-buildpackage a lot. But I don't understand what's "the right > way" to manage patches. > > The git-buildpackage manual suggests it's gbp-pq, which works on a > separate branch. I would have nothing against

Re: git-buildpackage and patches

2010-09-17 Thread Bernhard R. Link
* Pietro Battiston [100917 15:37]: > On the other side, using quilt is just fine... but I do find great the > idea that if you use a VCS, you _shouldn't_ need a separate tool for > patches. And indeed, I see sometimes git-buildpackage automatically > creates some patches named "debian-changes-x.y.

git-buildpackage and patches

2010-09-17 Thread Pietro Battiston
Hello, I like git-buildpackage a lot. But I don't understand what's "the right way" to manage patches. The git-buildpackage manual suggests it's gbp-pq, which works on a separate branch. I would have nothing against this approach, if it worked transparently. Instead, when I "import" and then "exp

Re: Doubts in Sigar packaging

2010-09-17 Thread Tony Houghton
On Fri, 17 Sep 2010 18:23:17 +1000 Matthew Palmer wrote: > On Thu, Sep 16, 2010 at 12:44:47PM +0100, Tony Houghton wrote: > > On Thu, 16 Sep 2010 19:00:27 +1000 > > Matthew Palmer wrote: > > > > > git --describe is, as far as I can tell, useless for the purpose > > > stated at the beginning of

Re: Doubts in Sigar packaging

2010-09-17 Thread Adam Borowski
On Fri, Sep 17, 2010 at 06:23:17PM +1000, Matthew Palmer wrote: > On Thu, Sep 16, 2010 at 12:44:47PM +0100, Tony Houghton wrote: > > Did you miss the bit? I think that makes it > > ideal provided each release is tagged with its version number. > > Because tags aren't globally unique. Since you y

Re: Doubts in Sigar packaging

2010-09-17 Thread Matthew Palmer
On Thu, Sep 16, 2010 at 12:44:47PM +0100, Tony Houghton wrote: > On Thu, 16 Sep 2010 19:00:27 +1000 > Matthew Palmer wrote: > > > > > On Wed, Sep 15, 2010 at 03:18:20PM +0200, Adam Borowski wrote: > > > > > Why won't you just use `git --describe`? > > > > > It produces nice version numbers of the

Re: RFS: flightgear, fgfs-base and simgear (updated packages) and 16 new flightgear related packages (attempt three)

2010-09-17 Thread Chris Baines
The main reason for the number of packages is to allow customisation. The reasons are different for the individual packages, for instance the scenery package is not needed if the user wants to use terrasync for scenery and the fgfs-base-models package is separated from the fgfs-base package so that