[3dprinter-general] Bug#706656: ITP: cura -- Controller for 3D printers

Gregor Riepl onitake at gmail.com
Sun Sep 25 12:40:42 UTC 2016


> Ok, I added you to the team.  Welcome. :)

Thanks, and hello everyone.

I've been a Cura 2 user for quite some time, and it would be nice to have it 
in the Debian repositories. Installing a monolithic package is not a good 
solution. Pulling in external package repositories (PPAs) isn't either.

To start off, I forked the official repositories on Github and added a debian 
branch on each, with packaging files:
https://github.com/onitake/libArcus
https://github.com/onitake/Uranium
https://github.com/onitake/CuraEngine
https://github.com/onitake/Cura

I'd also like to point out Thomas's packaging repository:
https://github.com/thopiekar/Cura-packaging

His package scripts are very similar to the ones I wrote, but they're more 
refined. Uranium is split into multiple packages and he has dependencies that I 
forgot.

I believe it's a good idea to continue with these and feed back any 
improvements so Thomas can incorporate them. For Debian packaging, however, it 
may be better to go with separate repositories.
I'm not familiar enough with the Debian release process yet, so I'd appreciate 
some input on how to do this properly (i.e. repos on Alioth, repos with only 
the Debian package files, etc.).

There are also a number of open questions, that are listed on the 
corresponding ITP: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706656

A summary:
- Bas has pointed out there may be non-free files left over in the source 
trees. I'm going to check this later.
- All code is licensed under AGPL-3+ - the sources in Uranium still need to be 
checked manually because it's missing a LICENSE file in the 2.1.3 release. 
master has it.
- libArcus has a bit of a version conflict. The project uses its own versioning 
scheme, but releases are tagged in line with the rest of the Cura projects. 
The library is named libArcus.so.1.0.0, the SONAME is libArcus.so.2 and the 
tag is 2.1.3. Weird, but should be ok. I think it's best to use the release 
tag as the package version, too.
- CuraEngine conflicts with cura-engine in Debian, due to the changed 
versioning. Adding an epoch, like 1:2.1.3, should "fix" this and make the 
package a simple "upgrade". Cura will depend on this particular version 
anyway, so it's upgraded automatically.
- Source code is compiled in-place, I'm not sure what options I need to pass 
to dh or cmake to make it use a separate build dir. dh clean does not seem to 
work properly either. (more testing needed)




More information about the 3dprinter-general mailing list