[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Newbie questions on packaging opencpn



On Tue, Sep 04, 2018 at 10:16:16AM +0200, Sebastiaan Couwenberg wrote:
> 
> There is value to autopkgtests, but can be quite time consuming to
> setup.

I found this a non-timeconsuming "setup"

   /usr/share/doc/pbuilder/examples/B20autopkgtest

to run it in every pbuilder.  Well, the *setup* is a non-brainer while
the test itself might take some time depending from the test.

>  I: unarr source: debian-watch-file-is-missing
> 
> This needs an override until a watch file can be added after upstream
> starts tagging releases.

I started using

   opts="mode=git,pretty=0.0+git%cd.%h"

for missing release tags.  Works out quite good and saves you
get-orig-source targets.
 
>  I: libunarr1: no-symbols-control-file
> usr/lib/x86_64-linux-gnu/libunarr.so.1.0.0
> 
> Since it's a C library adding a symbols files is a must, for C++
> libraries `dh_makeshlibs -V` or pkgkde-symbolshelper should be used.

I tend to think that it is not a "must" but rather "good style" and
would not ask beginners to provide symbols files.  I know there are
different opinions about this.  It can be a real nuisance packaging wise
if it comes to different symbols on different architectures / compiler
versions and getting a package out first and doing "good style" later is
a valid approach in my opinion.

Kind regards

      Andreas.

-- 
http://fam-tille.de


Reply to: