summaryrefslogtreecommitdiff
path: root/setup.py
Commit message (Collapse)AuthorAgeFilesLines
...
* setup.py: Use setuptools_scm pluginTristan Van Berkom2017-05-081-1/+2
| | | | | | | | | | 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.
* Install man pages in ${prefix}/share/man/man1Tristan Van Berkom2017-04-131-1/+1
| | | | Instead of ${prefix}/man/man1, share/man/man1 is more correct.
* Adding man pages to distributionTristan Van Berkom2017-04-131-0/+22
| | | | | | | | | | 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
* setup.py: BuildStream now depends on python 3.4Tristan Van Berkom2017-04-081-2/+2
| | | | | | 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.
* setup.py: Removing the xdg dependencyTristan Van Berkom2017-03-211-1/+0
|
* context.py: Now using the XDG Base Directory specTristan Van Berkom2017-03-201-0/+1
| | | | | | | | | | | | | | 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.
* setup.py: Added setuptools as install requirementTristan Van Berkom2017-03-081-1/+2
| | | | | | 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.
* Restructuring, moved frontend related files to _frontend/ submoduleTristan Van Berkom2017-03-071-2/+2
| | | | | Probably widget.py could be split up and cleaned up some more, but at least this puts the frontend out of the way.
* setup.py: BuildStream now requires blessings.Tristan Van Berkom2017-03-071-1/+2
| | | | | | 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.
* _sandboxbwrap.py: Force terminate sandboxed jobs when terminating a taskTristan Van Berkom2017-03-051-0/+1
| | | | | | | | | | | | | | | 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.
* setup.py: Check for the existence of BubblewrapPedro Alvarez2017-02-141-0/+9
| | | | | If this tool is not present in the system, BuildStream will fail to build anything.
* Adding new `bst` entry point for build-streamTristan Van Berkom2017-02-141-0/+1
| | | | | We will deprecate the `build-stream` script entry point but lets not remove it just yet.
* setup.py: Ensure OSTree version >= v2016.8Tristan Van Berkom2017-01-161-3/+18
| | | | | | | | 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.
* Moved frontend into buildstream package and build pipeline, use click.Tristan Van Berkom2016-12-311-2/+5
| | | | | | Use setuptools to create the actual frontend script automatically, keeping the frontend code inside the package just makes things easier.
* setup.py: Finally use click for this, not argparseTristan Van Berkom2016-12-311-1/+1
| | | | Click is a nicer command line parser tool than argparse.
* setup.py: Add element yaml files to the distributionTristan Van Berkom2016-12-311-1/+1
|
* setup.py: Require at least python 3.5Tristan Van Berkom2016-12-171-0/+4
| | | | | | | 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.
* Include coverage report in ./setup.py test invocationsTristan Van Berkom2016-12-111-0/+2
|
* Add pep8 checks to test suiteTristan Van Berkom2016-12-091-1/+4
| | | | Now when running ./setup.py test, pep8 linter checks are automatically run.
* setup.py: check for PyGObject and OSTree dependenciesJürg Billeter2016-12-011-0/+15
| | | | OSTree will be used for the artifact cache.
* setup.py: add missing sys importJürg Billeter2016-11-301-0/+2
|
* Adding InvocationContextTristan Van Berkom2016-11-141-1/+1
| | | | | | | | An object for collecting user preferences from config files and command line, this state is shared across recursive pipelines. Also adds the default configuration file and ensures that it's distributed into a data subdir.
* setup.py: Now require pytest-datafiles for testsTristan Van Berkom2016-11-131-1/+1
| | | | | A convenience module for staging data files to a directory for running tests which integrates as a pytest fixture.
* Use pytest, add first basic plugin testTristan Van Berkom2016-11-131-5/+22
|
* Added plugins as package data.Tristan Van Berkom2016-11-081-2/+9
| | | | | | | These are not part of the python package, but part of the data installed. Yes, it's a bit weird, but more correct than having the plugins as submodules of the actual buildstream python package.
* Adding initial setup.py file for setuptools.Tristan Van Berkom2016-11-081-0/+19
View Lorry Controller Status