> Von: Piotr Ożarowski [mailto:piotr@debian.org] > > [Fiedler Roman, 2016-06-09] > > > is AMiner and AMinerRemoteControl symlinked in /usr/bin/? > > > (you can use debian/logdata-anomaly-miner.links to do that) > > > > Currently they are not symlinked. I took the same approach as with > > e.g. /usr/lib/apt/methods/http or /usr/lib/eject/dmcrypt-get-device > > where those binaries are usually not intended to be called by user > > directly. Meanwhile this has changed, e.g. AMinerRemoteControl is more > > or less now OK for cmd-line use. So I would add the symlinks. Or would > > moving of the files be more Debianic? > > dh_python2 doesn't add interpreter to Depends for scripts that are not > in $PATH. That's why lintian complains. You can: > * symlink them in /usr/bin/ (or any other appropriate path) I did that, modification: $ cat debian/logdata-anomaly-miner.links /usr/lib/logdata-anomaly-miner/AMiner /usr/bin/AMiner /usr/lib/logdata-anomaly-miner/AMinerRemoteControl /usr/bin/AMinerRemoteControl > * drop executable bit from these scripts, if they're not meant to be > execute.... (IIRC lintian ignores shebangs in non-executable files) not an option > * or if they're meant to be executed, but you don't want them to be > available out of the box, add "python" to Suggests or Recommends There are some usecases for users to call them, so let's have them available also. Still lintian will complain about this file, current header: #!/usr/bin/python2 -BEsSt But as patching that to 2.7 will make the warnings go away, from my point of view, that workaround is sufficient for me. New package is uploaded. Are there any other open points I shall address?
Attachment:
smime.p7s
Description: S/MIME cryptographic signature