Commit graph

12 commits

Author SHA1 Message Date
Joshua Lock
de1a3af019 build: more intentional about what's included in sdist
Our sdist has typically included everything from git apart from the CI
related files (.github/*, .fossa.yml, .readthedocs.yaml). Update our
MANIFEST.in and the check-manifest section of setup.cfg to be explicit
about this.

Signed-off-by: Joshua Lock <jlock@vmware.com>
2021-10-21 13:30:46 +01:00
Joshua Lock
4fd35434bd build: update MANIFEST.in to match sdist
Update the MANIFEST.in to be explicit about what we choose to ship in our
sdist. This _does not_ result in any additional files being included in
our sdist, but does remove warnings from build.

Signed-off-by: Joshua Lock <jlock@vmware.com>
2021-10-21 13:28:08 +01:00
Philippe Coval
f496c83e78 docs: Remove academics files
Duplication is not needed since files are hosted in website project:

https://github.com/theupdateframework/theupdateframework.io/tree/master/static/papers

Those generated files are not explicitly under Apache-2.0 licence
and AFAIK they can not be regenerated from missing (latex?) sources.

To avoid licence mixup.
It would help to have those files published elsewhere.
Meanwhile online (Github) links are used.

Debian had to repack the source package to make tarball compliant with DFSG
despite debian tools are known to be trustworthy,
this extra step would add weakess in the chain of trust

Cleanup done upstream would make distribution safer.

Bug: https://github.com/theupdateframework/tuf/issues/1161
Bug-Debian: https://salsa.debian.org/python-team/packages/tuf/-/merge_requests/11
Relate-to: https://github.com/theupdateframework/tuf/issues/263#issuecomment-835239415
Forwarded: https://github.com/theupdateframework/tuf/pull/1380
Relate-to: https://github.com/theupdateframework/specification/pull/160
Signed-off-by: Philippe Coval <rzr@users.sf.net>
2021-05-28 17:07:14 -04:00
Philippe Coval
7e23201741 build: Add keys to sdist archive for tests
While packaging latest release for debian from pypi tarball
I noticed some tests' files were not shipped, let's add them.

Relate-to: https://github.com/theupdateframework/tuf/issues/263
Signed-off-by: Philippe Coval <rzr@users.sf.net>
2021-03-27 11:37:07 +01:00
Jussi Kukkonen
f3ab08d73f MANIFEST.in: Include LICENSE files
This seems to be a common way to handle license files. Also, vendoring
tool fails to handle tuf without a LICENSE file.

Fixes #1160

Signed-off-by: Jussi Kukkonen <jkukkonen@vmware.com>
2020-10-05 13:13:58 +03:00
Vladimir Diaz
8152483f93
Include correct README in MANIFEST.in
Signed-off-by: Vladimir Diaz <vladimir.v.diaz@gmail.com>
2018-06-20 17:50:41 -04:00
Vladimir Diaz
264cdf0674
Update MANIFEST.in following reorganization of directory structure
Signed-off-by: Vladimir Diaz <vladimir.v.diaz@gmail.com>
2018-01-31 17:33:14 -05:00
Vladimir Diaz
52b6d4ec5c Remove ssl_crypto references from MANIFEST.in 2017-01-13 11:06:59 -05:00
Artiom Baloian
7098cdbc3a Move _vendor dir and split formats into the formats and tufformats 2016-10-28 18:37:28 -04:00
Vladimir Diaz
f6ec7fb578 Remove _delete_obsolete_metadata() from developer_tool.py and update MANIFEST.in to list scripts. 2016-08-25 14:34:36 -04:00
Vladimir Diaz
2517bd1341 Update MANIFEST.in
Remove iso8601 entry
2016-01-22 11:09:55 -05:00
Vladimir Diaz
c20fd4afa8 Update release files. 2014-07-16 12:51:35 -04:00