| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In some cases, such as when working inside a virtual environment, it can
be desirable to install all dependencies for running tests using `pip`.
This is currently not possible since setuptools does not support
installing these dependencies in a virtual environment (by design).
(See https://stackoverflow.com/a/21003259.)
To circumvent this issue, move such requirements to
`dev-requirements.txt` file that can be used easily with
`pip install -r`. This also enables tests to be run directly using
`pytest`, which can be more convenient than `-addopts` approach when one
needs to add multiple options.
This will also be useful in creating better testuite images, and fix
some of the issues noticed in
https://gitlab.com/BuildStream/buildstream-docker-images/merge_requests/56.
|
| |
|
|
| |
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.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
