| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
jinja2 2.10 import time has been divided by two compared to Jinja 2.9.6
Fixes #194
|
|
|
|
|
|
|
|
|
|
|
|
| |
This removes most of the usages of pkg_resources from the codebase, helping
the goal of getting rid of that completely.
With this change, version number is generated during install and embedded into
`__version__` which is then imported by root level `__init__`. From there,
it is used by other parts of the codebase when needed.
Generated `__version__` file is ignored and not tracked by git to prevent
unnecessary 'changes' messages and accidental commits of that file.
|
|
|
|
|
|
|
| |
This change monkey patches setuptools' code generation functionality, so
that pkg_resources won't be imported in the generated file.
Fixes #172
|
| |
|
| |
|
|
|
|
|
|
| |
Our problem is with 4.4.2; and 4.2 lacks some features
and fails to collect all of the coverage from sub processes,
causing our reports to drop by 10%.
|
|
|
|
|
|
| |
This allows running tests in parallel:
./setup.py test --addopts "-n auto"
|
|
|
|
|
|
|
| |
Seeing random crashes with 4.4.2, these are solved by
simply using version 4.2.
Need to investigate and report proper bug to upstream for this.
|
| |
|
|
|
|
|
| |
Fixes the previous commits which attempt to allow optionally
only installing bst-artifact-receive, which doesnt work, because pip.
|
|
|
|
|
|
| |
A convenience to install `bst-artifact-receive` on an artifact server
that does not have the ostree and bubblewrap requirements to install
the main `bst` program.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The upstream of fuse.py is <https://github.com/terencehonles/fusepy>. It looks
pretty abandoned -- there have been no commits there since 5th April 2016 and
there are 17 pull requests dating from 2013 onwards that are still waiting for
responses from the maintainer.
There's no support in fuse.py for ppc64 platforms which means BuildStream is
unusable on that architecture at present. My pull request to fix that upstream
is being ignored; since the module is a single .py file provided under the
ISC license it is simplest to pull the whole thing into buildstream.git instead.
The version of fuse.py that's been embedded is the one from pull request #72,
from upstream release v2.0.4 (commit 0eafeb5).
|
|
|
|
|
|
|
|
| |
A previous change introduced the usage of pytest.param to our test
suite in commit 7aba0bfc906409073c4d246ec009a8622551726a.
This was only added to pytest 3.1.0, and the tests can't work with older
versions.
|
|
|
|
| |
Turns out we do need this in some corner cases
|
|
|
|
|
|
|
| |
Turns out this doesnt work once you try to actually
run the full buildstream in a test case (in foreground
it screws with other parsing, in background it fails
in the test context with a strange error).
|
|
|
|
|
| |
Currently this gets installed at ${prefix}/share/bash-completion/completions
but this is not exactly correct.
|
|
|
|
| |
Fixes #58
|
| |
|
|
|
|
| |
Added entry point for running `bst-artifact-receive`
|
|
|
|
| |
Including changes in _site.py and setup.py
|
| |
|
| |
|
| |
|
|
|
|
| |
We can start using those to assert the version >= 2017.4
|
| |
|
|
|
|
| |
Now you can only invoke BuildStream with the `bst` command
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This plugin automatically encodes git versioning information
into the package version string so that it shows up in `bst --version`
This versioning information is encoded into source distributions
as well, so that when installing from a source distribution without
the git repository the precise VCS provenance is still encoded into
the version.
|
|
|
|
| |
Instead of ${prefix}/man/man1, share/man/man1 is more correct.
|
|
|
|
|
|
|
|
|
|
| |
Man pages are automatically generated but unfortunately committed
to the repository, this should be fixed by integrating the man
page generation as a part of the build step, but this seems to be
very difficult and is not well documented at all.
Tip: The man_pages module of click_man implements a distutils.core.Command
for generating man pages, this command should be run as a part of setup.py
|
|
|
|
|
|
| |
It was now tested on 3.4, after a few changes it seems
to work well with 3.4, backing down the version requirement
as 3.4 is more widely available in today's distros.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
o Attempt to load user configuration from ${XDG_CONFIG_HOME}/buildstream.conf
if one exists, only if not overridden on the command line
o Set the XDG Base Directory values at initialization time
o Allow environment vars to be specified in paths
o userconfig.yaml: Default paths now use XDG_CACHE_HOME instead of ~/buildstream
o Removed the deploydir and ccache dir as we're not using those, we'll re-add those
configs if they become relevant.
|
|
|
|
|
|
| |
This is redundant in cases where setuptools is used to
install, but is pedantically correct since we use setuptools
in BuildStream to detect and print the package version.
|
|
|
|
|
| |
Probably widget.py could be split up and cleaned up some more,
but at least this puts the frontend out of the way.
|
|
|
|
|
|
| |
Blessings gives us some code for positioning the cursor on terminals
which support that (almost all terminals on linux), this lets us
print some things always at the bottom of the output.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a tricky problem because bwrap is a setuid root program which
we do not have permission to terminate.
To solve this, we ensure --unshare-pid is used (which should have been
there already probably anyway) which causes bwrap to create one additional
direct child process owning the created pid namespace.
Using psutil, we enumerate the direct child of the spawned bwrap process,
which we do have permission to kill, and kill that task directly.
Since all child tasks are spawned in a pid namespace, they are automatically
killed once the owning process of that namespace exits.
|
|
|
|
|
| |
If this tool is not present in the system, BuildStream will
fail to build anything.
|
|
|
|
|
| |
We will deprecate the `build-stream` script entry point but
lets not remove it just yet.
|
|
|
|
|
|
|
|
| |
There is no easy way to check the version we need for
OSTree with introspection, we only have version "1.0".
So we try to access a method directly and bail out
if it doesnt exist.
|
|
|
|
|
|
| |
Use setuptools to create the actual frontend script automatically,
keeping the frontend code inside the package just makes things
easier.
|
|
|
|
| |
Click is a nicer command line parser tool than argparse.
|
| |
|
|
|
|
|
|
|
| |
We require ostree from July 2016 and we also require bubblewrap,
both of which are more recent than python 3.5 which was released
in September 2015. There is no point to have version conditional
code here or support earlier versions of python.
|
| |
|
|
|
|
| |
Now when running ./setup.py test, pep8 linter checks are automatically run.
|
|
|
|
| |
OSTree will be used for the artifact cache.
|
| |
|