debian packaging

[LucidOne]

Does artoolkit need to be forked to make this happen?

[LucidOne]

I think artoolkit needs to be forked to get this into bloom/ros build farm

[dlaz]

What exactly is the issue preventing a release? Is it just hosting the tarball somewhere reliable, or is there something the build process doesn't like about how artoolkit gets built? If it's a hosting issue, it's small enough that it could probably be hosted on github. We could also think about releasing artoolkit separately as a 3rd party package (http://wiki.ros.org/bloom/Tutorials/ReleaseThirdParty).

[LucidOne]

So based on my discussions, given the state of ARToolKit it looks like there are a few ways forward.

Fork ARToolKit and use the github releases feature to host a tarball then make a debian release using bloom as a third party release. This would involve getting autoconf to wok with bloom.

Another approach that might be less work is to fork ARToolKit and port the build system to CMake and just release it as a regular ROS package.

The third approach is fork, port the build system to CMake and keep it as a non-ROS package and continue to release it as a third party package. This might be the best option because we could try to get it into Debian.

[dlaz]

Porting to CMake will probably make a lot of things easier, though that doesn't seem like a fun job.