Hi Robert,

On 2/4/09, Robert Osfield <robert.osfi...@gmail.com> wrote:
> Hi All,
>
> Now that I've tagged 2.8.0-rc1 my focus has now moved on to helping
> out on the packaging front.  The packaging that I'd like to contribute
> is the debian packages, so I've started down this journey by enable
> cpack support in the OSG, then doing:
>
> cpack -G DEB --config CPackConfig-libopenscenegraph.cmake -D
> CPACK_PACKAGE_CONTACT="rob...@openscenegraph.com"

very cool. To bad I haven't had the time to dig out the debian
generator features yet. I will eventually get to improving these but
as I realized that I wouldn't make it to 2-8 and that we have a man on
making debian packages I dropped it for now. See

http://packages.qa.debian.org/o/openscenegraph.html

for status of the openscenegraph debs. It seems that he has requested
help to get packages delivered and that Alberto Luaces and some others
have agreed to help him.

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=392266

For ubuntu it the ubuntu-MOTU developers are responsible for the
openscenegreph package(s) so we might need to poke them.

>
> Which generates a OpenSceneGraph-2.8.0.deb, which is but... if I then
> do create a package libopenscenegraph-dev pacakge I also get an
> OpenSceneGraph-2.8.0.deb.
>
> Looking at the CPackConfig-libopenscenegraph.cmake I note the
> CPACK_PACKAGE_FILE_NAME is OpenSceneGraph-2.8.0 which goes a long way
> to explain why the name is what it is.  I have been able to override
> it using:
>
> cpack -G DEB --config CPackConfig-libopenscenegraph.cmake -D
> CPACK_PACKAGE_CONTACT="rob...@openscenegraph.com" -D
> CPACK_PACKAGE_FILE_NAME="libopenscenegraph-2.8.0.deb"

All this is due to the workaround I had to do to make the tar archives
look like we wanted them with a top folder OpenSceneGraph-2.8.0 and
all the different packages would sort themselves in under that. My
first submission had debian-like packages names. I (or someone) will
have to fix this before we can make proper debs. What you have already
done (-DCPACK_PACKAGE_NAME=...) is probably a good solution that one
could put in an add_custom_target.

>
> I don't yet have the right architecture info in the debian name, and
> no doubt other items aren't yet set which I'll need to add.  I found
> the following page on the CMake/CPack wiki:
>
>   http://www.vtk.org/Wiki/CMake:CPackPackageGenerators
>
> I do wonder whether there isn't some more we could be doing on the
> generation of the CPackConfig-* files such as setting the base name a
> bit more appropriately.  I'm rather new to cpack and debian packaging
> so I'm rather floundering around a bit clueless, but that's how we
> start learning is it not...  Feel free to point me in the right
> direction.

There are some other cmake vars that are/will be used to create the
control file that must be part of every deb package. I think the only
one that we don't have in the CPackConfig-xxx scripts is the
CPACK_DEBIAN_PACKAGE_DEPENDS
...which I have fiddled with but not enough to dare a submission.
Perhaps someone more exerienced with debian cuold fill this out
properly. I will need to get some information from a real package
maintainer to fix this.

>
> In particular I'm keen to QA the packages I create, is there such a
> tool for debian?

Can't help here I'm afraid. I see that this mail didn't help much at
all but telling you things you already know :-( So to try and help I
mailed some questions to the ubuntu-motu developers mailing list
asking how we can help getting osg-2.8 into ubuntu packages adn will
persue that. For debian perhaps Alberto Luaces or someone else can
fill us in on how the debian package is doing and if any further help
is needed.

cheers
Mattias

>
> Robert.
> _______________________________________________
> osg-users mailing list
> osg-users@lists.openscenegraph.org
> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
>
_______________________________________________
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Reply via email to