Hey Guys, we have a continuous integration setup here at Siemens. Next to our own repos we also compile and test upstream to detect problems before merging. I know the changes to the debian directory seem unimportant, but our current CI infrastructure is built on that. So please consider applying my suggestions. Using the CI we hope to find and fix issues in the whole project but for that to work we need a reliable way of deploying binaries to our test systems.
If there is a debian directory in the tree, it should be consistent. The other option would be to remove it all together, i personally prefer the first option. regards, Henning On Thu, 30 Apr 2015 13:59:54 +0200 Henning Schild <[email protected]> wrote: > Since 8871363fa57266af4c8d8a06965f2898b940fb48 the binary and its > man-page are in the base package (xenomai-runtime). Remove the files > from the -dev package to resolve the current package conflict. > > Signed-off-by: Henning Schild <[email protected]> > --- > debian/libxenomai-dev.install | 2 -- > 1 file changed, 2 deletions(-) > > diff --git a/debian/libxenomai-dev.install > b/debian/libxenomai-dev.install index 40ae57d..7b107cb 100644 > --- a/debian/libxenomai-dev.install > +++ b/debian/libxenomai-dev.install > @@ -1,8 +1,6 @@ > -usr/bin/xeno-config > usr/include > usr/lib/*.la > usr/lib/*.a > usr/lib/*.so > usr/lib/cobalt.wrappers > usr/lib/dynlist.ld > -usr/share/man/man1/xeno-config.1 _______________________________________________ Xenomai mailing list [email protected] http://xenomai.org/mailman/listinfo/xenomai
