Re: [MoM] Packaging OpenSurgSim
On Mon, 2015-01-26 at 17:36 +0100, Andreas Tille wrote:
> > Should I get in touch with the maintainer of Debian
> > yaml-cpp to see if I can help getting the new version packaged?
>
> This sounds sensible. Considering the old debhelper and Standards-Version
>
> $ apt-cache showsrc yaml-cpp
> Package: yaml-cpp
> Binary: libyaml-cpp0.5, libyaml-cpp-dev
> Version: 0.5.1-1
> Maintainer: Lifeng Sun <lifongsun@gmail.com>
> Build-Depends: debhelper (>= 7.0.50~), cmake, libboost-dev
> Architecture: any
> Standards-Version: 3.9.4
>
>
> it was not maintained for some time. Offering help (perhaps inside
> collab-maint VCS) would probably enhance chances to get things happening
> more quickly.
OK, I contacted the yaml-cpp maintainer and offered help.
> > Also, there are a couple of more packaging questions:
> >
> > - The policy mentions adding "Testsuite" field to the debian/control
> > file. OpenSurgSim uses CTest to run our Google Test unit tests. The
> > tests seems to be running correctly during the build. But, what do I
> > need to put in this field?
>
> The testsuite field can stay empty but it would be great to run also
> autopkgtest (in debian/tests). There is a difference between tests run
> at build time and testing ready built binaries fetched from Debian
> mirror. We should provide both if possible.
I am trying to figure out what this should be. I was thinking about what
would test that the package is installed correctly. How about a small
sample application consisting of a CMakeLists.txt and a simple cpp. The
CMakeLists.txt would check that cmake could find OpenSurgSim, and the
cpp would do something really basic. This would require gcc and cmake to
run. Is this along the lines of what you are thinking of?
> > - README.test and README.source, I am a little confused as to what goes
> > here. Is there an example I can look at?
>
> We have several examples in Debian Med repository. You might also try
> codesearch - here is a quite naive example that probably could be
> enhanced:
>
> http://codesearch.debian.net/results/debian%2Ftests%2Fcontrol/page_0
Wow, codesearch is a great tool. Thanks for pointing it out.
> > - debian/upstream (or debian/upstream/metadata). I would like to add
> > this as well. Again, do you know of a good example I can follow?
>
> I created a package template (see Debian Med team policy) which also
> contains a boilerplate:
>
> http://anonscm.debian.org/viewvc/debian-med/trunk/package_template/upstream/metadata?view=markup
I pushed an upstream/metadata file to the repository, let me know if you
see any issues.
Is there anything else I should be doing while I wait for yaml-cpp to be
updated?
-Paul
Reply to: