[Bug 1503915] Review Request: roca-detect - test RSA public keys for ROCA vulnerability

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



https://bugzilla.redhat.com/show_bug.cgi?id=1503915



--- Comment #22 from Stuart D Gathman <stuart@xxxxxxxxxxx> ---
(In reply to Miro Hrončok from comment #21)
Look, I really appreciate the nits you've pointed out, and I've learned a lot.
But let me turn it around.  Upstream provides two directly executable CLI
python scripts in %{py_sitelib}.  I symlink them to /usr/bin for convenience. 
Why are you so against that?  All my packages have one or more symlinks for
convenience, I've never encountered any resistance from reviewers over it
before.

My (admittedly snide, sorry) remark about the teleology of EASY scripts was
based on my observation that they work on Windows, do not work for me out of
the box on Fedora (I know you said installing some additional stuff would let
them work), and when I trace through the source to debug, I find they end up
doing the equivalent of simply symlinking the actual CLI scripts.  Is there a
Fedora rule against using symlinks to conveniently access python CLI scripts? 
Without the symlink, you could also just type "python3 -m roca.detect" as the
equivalent of the /usr/bin/roca-detect symlink.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component
_______________________________________________
package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to package-review-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/package-review@xxxxxxxxxxxxxxxxxxxxxxx




[Index of Archives]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite Conditions]     [KDE Users]

  Powered by Linux