[3dprinter-general] Bug#706656: ITP: cura -- Controller for 3D printers
wijnen at debian.org
Wed Apr 5 06:40:17 UTC 2017
-----BEGIN PGP SIGNED MESSAGE-----
On Tue, Apr 04, 2017 at 11:36:37PM +0200, Gregor Riepl wrote:
> > Of course it is still useful to have your packaging (the debian directory)
> > under version control as well, and using names for those releases also
> > makes sense. If you want to name them debian-* that's fine, although given
> > that they only contain the debian directory, it doesn't seem like it would
> > confuse anyone anyway.
> Well, this is the best way to do it when using git-buildpackage.
> If you have other suggestions, I'm all ears. :)
I agree this is the best way; my point was that you should not have a
repository on github with a copy of the source, and the watch file should point
to Ultimaker's github. Having a repository with the packaging is good. You
can also host that in our team repository on Alioth. You are a member with
> If at all possible, I'd like to stick to cmake modules and not use anything
> external like pkg-config.
> Or maybe there's a cmake module for pulling in information from .pc files?
It seems like there is:
> >> Cura's clipper consists of two files and has no external dependencies. I
> >> don't think repackaging it is worth the effort. Should a
> >> security-critical bug be discovered, it's not going to be too hard to
> >> convince the Cura developers to patch CuraEngine.
> > When I packaged the previous version of Cura (of which only CuraEngine made
> > it into Debian), I thought it was worth the effort, so luckily for you I
> > already packaged it. :)
> Ok... If it doesn't require too many modifications in the build system.
It shouldn't. Worst case, you can remove the bundled files and replace them
with symlinks as part of the build. But using pkg-config is better; if
anything changes, that will change with it and it will continue to work.
> > I tried the earlier version from you, which was also unusable for me
> > because it didn't support delta printers. I downloaded their new release
> > (2.4), which works fine for me.
> It did - if you built your own printer definition with a custom keepout area
> like I did. ;)
Ah yes, I heard someone talk about that, and was told that it worked, but
getting 2.4 was the easier fix for me. :)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
-----END PGP SIGNATURE-----
More information about the 3dprinter-general