| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add `.in` and `.txt` requirements files for BuildStream's pure python
dependencies. For each pair, the `.in` file is supposed to capture the
loose version requirements, and the corresponding `.txt` file is
supposed to have frozen requirements. We have 3 such sets:
* `requirements`: BuildStream's runtime dependencies
* `dev-requirements`: Dependencies for running tests
* `plugin-requirements`: Dependencies for core plugins
Note that the frozen requirements files will only be used for testing
purposes, and `setup.py` will continue to read loose requirements.
This commit comes with a Makefile to update the requirements files as
well.
---
!1027 is related MR for the master branch.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently, running any setuptools commands using `setup.py` generates a
warning like so:
warning: manifest_maker: MANIFEST.in, line 21: unknown action 'dev-requirements.txt'
The syntax is invalid and got accidentally introduced in !637 but it's a
shame that this is not a warning and no obvious way to make it an error
if there are invalid things in MANIFEST.in file.
---
This is a backport of
https://gitlab.com/BuildStream/buildstream/merge_requests/704.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is backport of !637 to bst-1.2.
There were a couple of differences between the requirements listed in
the `master` branch and the `bst-1.2` branch so I have left them
untouched.
For reference, here are the differences between them:
```diff
--- a/dev-requirements.txt
+++ b/dev-requirements.txt
@@ -2,8 +2,9 @@
# random crashes with 4.4.2
coverage == 4.4.0
pep8
+pylint >= 1.8 , < 2
pytest >= 3.1.0
-pytest-cov >= 2.5.0
+pytest-cov
pytest-datafiles
pytest-env
pytest-pep8
```
|
| |
|
|
| |
This allows code generation with ./setup.py build_grpc
|
| |
|
|
|
|
|
| |
Correct includsion of buildstream.doap which does not exist
to 'include BuildStream.doap'.
This commit resolves issue #430
|
| |
|
|
|
| |
We don't have `Dockerfile` and `Dockerfile-build.sh` anymore in this
repository so remove them from `MANIFEST.in`.
|
| |
|
|
| |
Some basic module metadata before publishing the 1.0 release.
|
| |
|
|
|
|
|
|
|
| |
This test should contain an entry for every element and source plugin
in buildstream. Further, an entry should exist for every feature of
every plugin which may effect cache key calculation.
MANIFEST.in: Adding .expected files used in this test to the
generated dist tarballs.
|
| | |
|
| |
|
|
|
| |
Now that we distribute generate-ostree.sh in the tests we
will need it to run tests from a distributed tarball.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
