Bug#777000: ITP: limereg -- Lightweight Image Registration. Commandline application for image registration (automatically aligning two images with similar content).

[Roelof Berg]

Hi Anton and List,

thanks for the clarification, packaging is new to me. I will follow that 
example for lib, lib-dev, lib-src (maybe I have only access to 
debian-science, then I will look there for a similar example).

Please allow me a question, I have two projects that are closely 
connected to each other - but also independent in some way:
a) A library 'liblimereg'
b) A command line utility 'limereg' (that uses liblimereg today - but 
could in theory use something else in the future, or additional libs for 
that purpose)

The commandline-tool is _not_ meant as a tool for the library. It is 
meant as a standalone application for end-users that are no programmers, 
and will have less release cycles than the lib. The lib will have more 
customers than limereg (maybe OpenCV and ImageMagick, if I'm allowed to).

As upstream (which is me) I use two distinct github projects with 
different version numbers, branches, prerequisites etc. for both.

Would it in that case make sense to have two packaging projects ? One 
called 'limereg.lib' for the application and one called 'liblimereg.lib' 
for the library (containing -dev, -src, -dbg etc.). Or should I try to 
combine the two upstram-repos  in one packaging project ?

Thanks a lot,
Roelof

On 19.02.2015 22:34, Anton Gladky wrote:
> Hi Roelof,
>
> 2015-02-19 22:08 GMT+01:00 Roelof Berg <rberg at berg-solutions.de 
> <mailto:rberg at berg-solutions.de>>:
>
>     If this naming scheme is ok, I will add:
>     packages/limereg.git (Shell application for image registration)
>     packages/liblimereg.git (Library for image registration - used by
>     the shell tool above)
>     packages/liblimereg-dev.git (Library with headerfiles)
>
>     Later I could also add liblimereg-dbg (debug symbols) and
>     liblimereg-src (sourcecode), if this makes sense.
>
>
> Hmm, I do not quite understand, why do you need separate git-repo for
> each binary? See for example how freeglut library os packaged [1]. There
> is also -dev, -dbg and library itself.
>
> [1] https://packages.qa.debian.org/f/freeglut.html
>
> Best regards
>
> Anton

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/debian-science-maintainers/attachments/20150219/55e9d019/attachment-0001.html>