Hi, > 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. I did cut down on them a bit, but the packages are still not done yet. > Not many I suppose, but if we all follow this rule, it may make it easier for > programs to display the information is a good way. In a case like this, even > if I wouldn't be able to come up with a reason for the rule, I'd fix it anyway > because it's so easy to do. Please excuse me, then. I will take more care about these things from now on. > 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 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. > Even simpler is to set the debhelper compat level to at least 10. It will > default to enable all hardening. (I didn't check the current level, but if it > is 10 and there's no hardening, it must have been explicitly disabled somehow.) Ok, I will test that. >> 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. Best regards, Greg
Attachment:
signature.asc
Description: OpenPGP digital signature