-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add LICENSE file and tests to PyPI sdist #166
Comments
uqs
pushed a commit
to freebsd/freebsd-ports
that referenced
this issue
May 14, 2019
…rpose routines securesystemslib supports public-key and general-purpose cryptography, such as ECDSA, Ed25519, RSA, SHA256, SHA512, etc. Most of the cryptographic operations are performed by the cryptography and PyNaCl libraries, but verification of Ed25519 signatures can be done in pure Python. WWW: https://github.com/secure-systems-lab/securesystemslib [1] secure-systems-lab/securesystemslib#166 [2] secure-systems-lab/securesystemslib#167 git-svn-id: svn+ssh://svn.freebsd.org/ports/head@501637 35697150-7ecd-e111-bb59-0022644237b5
uqs
pushed a commit
to freebsd/freebsd-ports
that referenced
this issue
May 14, 2019
…rpose routines securesystemslib supports public-key and general-purpose cryptography, such as ECDSA, Ed25519, RSA, SHA256, SHA512, etc. Most of the cryptographic operations are performed by the cryptography and PyNaCl libraries, but verification of Ed25519 signatures can be done in pure Python. WWW: https://github.com/secure-systems-lab/securesystemslib [1] secure-systems-lab/securesystemslib#166 [2] secure-systems-lab/securesystemslib#167
swills
pushed a commit
to swills/freebsd-ports
that referenced
this issue
May 14, 2019
…rpose routines securesystemslib supports public-key and general-purpose cryptography, such as ECDSA, Ed25519, RSA, SHA256, SHA512, etc. Most of the cryptographic operations are performed by the cryptography and PyNaCl libraries, but verification of Ed25519 signatures can be done in pure Python. WWW: https://github.com/secure-systems-lab/securesystemslib [1] secure-systems-lab/securesystemslib#166 [2] secure-systems-lab/securesystemslib#167 git-svn-id: svn+ssh://svn.freebsd.org/ports/head@501637 35697150-7ecd-e111-bb59-0022644237b5
Jehops
pushed a commit
to Jehops/freebsd-ports-legacy
that referenced
this issue
May 14, 2019
…rpose routines securesystemslib supports public-key and general-purpose cryptography, such as ECDSA, Ed25519, RSA, SHA256, SHA512, etc. Most of the cryptographic operations are performed by the cryptography and PyNaCl libraries, but verification of Ed25519 signatures can be done in pure Python. WWW: https://github.com/secure-systems-lab/securesystemslib [1] secure-systems-lab/securesystemslib#166 [2] secure-systems-lab/securesystemslib#167 git-svn-id: svn+ssh://svn.freebsd.org/ports/head@501637 35697150-7ecd-e111-bb59-0022644237b5
Thanks for the request, @koobs. I'll look into it! |
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Downstream packagers like to use PyPI for (source) distribution files, and have those sources contain a LICENSE file and tests so we can distribute them along with any packages we ship to users, and properly QA the package locally.
At least: add
LICENSE
and grafttests/
inMANIFEST.in
, but preferably also add all requirements files and tox.ini/.travis.yml as they are good references for packagers to use, particularly as dependencies are often inconsistently/incorrectly declared in different places.Our case: I'm updating the existing FreeBSD port for tuf, and currently creating a port for securesystemslib for it to depend on.
Thanks!
The text was updated successfully, but these errors were encountered: