Bug#706656: [3dprinter-general] Bug#706656: ITP: cura -- Controller for 3D printers
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
On Mon, Mar 27, 2017 at 09:04:21AM +0200, Gregor Riepl wrote:
> > It looks like this has been forgotten? I would like to get Cura into Debian,
> > so if there's anything I can do to help, let me know.
>
> I'm sorry for the lack of action on my part, progress was stalled since some
> of the criticised points are a bit difficult to fix, and I've been too busy to
> invest much time into the them.
No problem, thanks for working on it!
> I did cut down on them a bit, but the packages are still not done yet.
Cool. I'm sure we'll get there. :)
> > This is quite confusing, and I would prefer to make it right in Debian. And of
> > course try to convince upstream to make it right as well. I'm not sure if it
> > generates junk; it might. You should run piuparts to see if ldconfig creates a
> > symlink that is not cleaned up on package removal.
>
> I reported the issue upstream, but haven't received a conclusive repsonse:
> https://github.com/Ultimaker/libArcus/issues/52
That looks good. I hope they will respond. It is bad for users if Debian's
and upstream's SONAMEs are incompatible; if they install something from us and
from online, it will break things.
> One of my suggested options would require changing upstream versioning
> altogether, the other would assimilate the Debian package version to what they
> are already using. And awhienstra said they would be changing Arcus versioning
> anyway.
>
> So I'm not sure what to do.
The important part in terms of compatibility is the SONAME. So the version of
the package doesn't really matter, but the files and symlinks in /usr/lib
should be properly named, and if possible, the SONAME should be identical to
what upstream uses.
> >> Also, CuraEngine is a core component of Cura, and while I assume it can be
> >> used standalone, it's usually not meant to be executed from the command
> >> line.
> >
> >> But I can take a look and provide a simple man page, if that's desired.
> >
> > No, you don't need to do that. As you say, it's not meant to be used directly.
> > That means two things: it doesn't need a manpage, and it must not be in the
> > (default) executable path. So install it under /usr/lib/cura/ or
> > /usr/lib/cura-engine/ and make sure the cura package calls it from there.
> >
> > This means you do need to change the cura source, I suppose, but in this case
> > that's part of integrating the program with Debian, so it is "strictly
> > necessary".
>
> I'm a bit reluctant to do this, as it will introduce additional maintenance
> overhead. But if this is the 'proper' way to go, I'll look into it.
Well, the other option is to say that users can use it directly. This is a
reasonable thing to say; I'm actually planning to set up some automated slicing
system which uses only the engine, not the gui. So in that case, it should be
in the executable path, and it should also have a manpage. For programs like
this, most of that manpage can be the contents of the --help output.
As for the capitals in the filename: I don't think there's a rule against it.
Most programs don't have capitals in them, so you could ask upstream to
consider changing it (but you can also not bother them), but it's not a big
deal, and having the same name as upstream is more important than it being
lowercase.
Thanks,
Bas
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBAgAGBQJY2N/gAAoJEJzRfVgHwHE6fl8P/1EabLSF7TUxKvv/jafwwHs0
hTTAjmqy2qgsA/dFN3X2YIMKmX14cxf5fXd3XZ0ASYAWPSKA7hLcTwN4hH8aM69Y
8fB7EYAq2O0COZ7txPRKp4nWXxX8Rn2zoaFpnXEKgjgRNIcZjtl4sT4JoNR2MFu/
T8Hv/8MjVLB5IdoKCX0eaWhE2DlT3Cd+o4n4q1x65vFhbt9f61SYto+kHCRfc7qA
nq4k8O3fxPdEpZkh89P/5ra8TTQhxvvStNsZHUNaT3TXVS5WIMOZA28RzDvP4Y77
ISyQ81eLOmdGZT8VoGHqbwH1Pj3iW9eddOSymR+mi1m1IzNB7jmBHQdLff3HbzPT
SI1BotEO8krT8okKqMEjK46zbabjhh6tcvSWPV9olylCM8zyRns9WYdtVMsxhiij
FMZqTCMpKfV3cBMbwyxqLXfB/ArQyDT4eFgKGGrqhOoIvBHlConYjWA2+q+rKOHi
zBXH5gL6WCbdjIiGpvgQKvA5z+Hx3eCJh9pXVK7lAH+5Ylpqfl1qO5yLvjAnqO9N
gFjhk+xjSrh4+7PnYHm6W8nHti/jWQW9FVLtfS1nmfHmBoMPR9ac46CROA29JB7y
TNi/qpTv2fRImhhRP+NxhlBiD1Wy8PSTxhm6PMzTjebmwpKIRzjrukVvQtpVo4WA
cJQiM/pLA+TSrwqJxyu1
=NPau
-----END PGP SIGNATURE-----
Reply to: