Re: Creating packages for one of my C project

2016-08-01 Thread Gianfranco Costamagna
>I'm not sure I follow. Three binary packages (lib, dev, doc) is fairly >standard for a shared library package. I would expect each git repo to >be a separate source package, unless they are very tightly coupled together. that was what I meant :) the doc can be the doxygen for the library, or so

Re: Creating packages for one of my C project

2016-08-01 Thread James Cowgill
Hi, On 01/08/16 16:43, Gianfranco Costamagna wrote: >> I would like to create 3 packages for the core part: lib (for the shared >> library object), dev (for headers), and doc (for documentation generated by >> doxygen). > > > maybe two binaries? I guess you need one package for each repo. > e.

Re: Creating packages for one of my C project

2016-08-01 Thread Gianfranco Costamagna
Hi, >I would like to create 3 packages for the core part: lib (for the shared >library object), dev (for headers), and doc (for documentation generated by >doxygen). maybe two binaries? I guess you need one package for each repo. e.g. git1 providing the lib and headers git2 providing the core

Creating packages for one of my C project

2016-08-01 Thread Nicola Spanti
Hi.First, let's be clear. I currently do not want to have an active activity as a Debian maintainer. I recently created a free/libre C project, and I would like to create clean Debian packages for it, and integrate them in Debian main. I have no problem to be the maintainer of them, but currentl