Re: [MoM] Packaging OpenSurgSim
Hi Paul,
On Fri, Jan 23, 2015 at 08:45:29AM -0500, Paul Novotny wrote:
> > as Debian Med policy recommends? You can do this even now. Please make
> > sure you push all branches after doing this.
>
> Oops, just forgot to push all branches. printine-tar and upstream are
> there now.
No problem. Just fetched it and when building in a chroot (you should
configure git-buildpackage to use cowbuilder as written in Debian Med
policy) I get (as expected after your last mail):
CMakeFiles/yaml-cpp.dir/build.make:86: recipe for target 'yaml-cpp/src/yaml-cpp-stamp/yaml-cpp-download' failed
> > Hmmm, just spekulating since I'm lazy and would like to wait for the
> > branches mentioned above and thus not trying the build: If this lib is
> > needed I'd expect libyaml-cpp-dev in the Build-Depends but havn't seen
> > it there.
>
> yaml-cpp is needed, but a patched version. OpenSurgSim builds
> libyaml-cpp during it's build, but currently there is no cmake rule to
> "install" libyaml-cpp.so, so the debian packaging can "install" it. I am
> working on fixing this at the moment, so that when packaging does this:
>
> dh_install -p$(pkg_lib) --autodest usr/lib/lib*
>
> libyaml-cpp.so will be alongside the other libs, and will be packaged.
As written before: This is not the way to go.
> > I think this is actually a *related* note. Does this "unsuccessful so
> > far" mean upstream has a problem to integrate the changes or did not yet
> > released a version which does contain the changes? Its Debian policy do
> > use the packaged version of libraries if at all possible (=you should
> > try hard to make it possible).
>
> "Unsuccessful so far" means I have sent patches to yaml-cpp almost a
> year ago (Feb 2014), but they haven't been integrated yet. The upstream
> author seems busy, as there hasn't been a new release of yaml-cpp since
> April 2013. I will continue to pester though. :-)
I have not yet tested this approach and your mileage may vary but you
might like to send the patches in a wishlist bug report to the Debian
package. On one hand it might solve your current build problem very
easily and on the other hand it might convince upstream if a major
distribution has the patches.
> > If you will not succeede in convincing upstream you could add it either
> > as quilt patch but this is probably to large. You can a also add it as
> > debian/<my_patched_source.tar.gz> and unpack it in debian/rules wherever
> > it is needed.
>
> Good idea, I'll implement this, but also keep trying to get our changes
> into yaml-cpp.
OK.
Kind regards
Andreas.
--
http://fam-tille.de
Reply to: