[Debian-med-packaging] libqes ready for review/upload

[Andreas Tille]

On Mon, Nov 16, 2015 at 07:15:48PM +1100, Kevin Murray wrote:
> > 
> > I personally do not create any symbols files since it creates manual
> > work for most version upgrades and sometimes even create additional work
> > for specific architectures.  For low popcon packages as ours this
> > admittedly sloppy attitude should be OK.  It would be perfect if you
> > would set higher standards for the packages you maintain and do the
> > manual work but several Debian Med packages come without symbols files.
> 
> OK, cool. If I find an easy to follow tutorial, I'll do so, otherwise I won't
> stress.

Fine.  BTW, as far as my past experience concerns it was not to hard to
follow the tutorial.  I'm just to lazy to follow it again and again for
new versions for a usage I consider very small.  Its rather the fact
that I need to continuosely need to spend time into something than that
it would be specifically hard.
 
> > I have two further remarks to the packaging:
> > 
> >   1. debian/watch contains
> >         repacksuffix=+dfsg,dversionmangle=s/\+dfsg.*//,
> >      I do not see any need for these manglings
> > 
> 
> Doh! That's what happens when I copy and paste. Thanks for catching that. I've
> fixed and pushed.

:-)
 
> >   2. I'm personally a big fan of d-shlibs and I'd recommend using it for
> >      library packages.  If needed I can send pointers for example packages.
> > 
> 
> Some pointers to examples and background on why you are a fan would be great. I
> had copied a d-shlibmove call in from bamtools (I think) as I was having
> trouble, but I couldn't get it working so I removed it and used *.install. I'm
> keen to do things properly though.

There is no such thing like "proper or not proper" here.  The resulting
package should be perfectly the same.  The reason why I'm a fan of
d-shlibs (and I'm using it in all my lib* packages) is that it does
certain sanity checks whether library policy is implemented correctly.
For instance it checks Depends/Conflicts in debian/control, checks for
proper naming of the packages etc.  If you do this manually *.install is
fine.  I simply think that the more automatic checks I'm using the
chance to make mistakes are lower.

Bamtools should be a sensible example - feel free to ask here in case of
trouble and I'd happily help to sort it out.  I agree that d-shlibs might
drain some patience if you start using it but once you understood the
principle its not that hard.
 
> Another questions, is a debian/debversion tag required on upload? I don't see
> one for libqes.

For packages in new I personally do not add any tags as long as the
package is not yet in unstable.  (It happens that I forget the tagging
once it is accepted but that's another story. :-)).  When sponsoring
packages I usually leave the tagging as a task for the sponsee - but in
principle everybody has permissions to set tags - so feel free to set it
whereever you consider that a missing tag should be set.
 
Kind regards

       Andreas.

-- 
http://fam-tille.de