| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
| |
Upstream have not released a new version since April 1997.
Additionally, newer daemons and applications are inconsistent in their
support for libwrap, leading to confusion as to whether an application
supports the library.
|
| |\
| |
| |
| |
| | |
Reviewed-By: Sam Thursfield <sam.thursfield@codethink.co.uk>
Reviewed-By: Richard Maw <richard.maw@codethink.co.uk>
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Try to be as generic as possible and only make a few exceptions:
- Only build ARM-related drivers if we are in ARM, this is:
nouveau,freedreno,vc4 (and svga,swrast as fallbacks)
- enable-gallium-egl only in ARM (needed by freedreno, nouveau)
- For the rest of the arquitectures, the drivers to build will be the
default ones, this is:
- DRI: i915 i965 nouveau r200 radeon swrast
- Gallium: r300 r600 svga swrast
- enable GLES2 (disabled by default)
- disable GLX (enabled by default) to not pull x11 deps
The rest all the configure parameters will be automatically configured
by the mesa's configure.ac
|
| | | |
|
| |\ \
| |/
|/|
| | |
Reviewed-By: Paul Sherwood <paul.sherwood@codethink.co.uk>
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
It only contains genivi layer_management component, but this component
seems to be replaced by wayland-ivi-extension present in
weston-genivi
|
| |/
|
|
| |
Its not a dependency of any stratum or system
|
| |\
| |
| |
| |
| | |
Reviewed-By: Richard Maw <richard.maw@codethink.co.uk>
Reviewed-By: James Thomas <james.thomas@codethink.co.uk>
|
| | | |
|
| | |
| |
| |
| | |
This version adds GL support
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
At this point we already have all the graphic libraries in the
system, so we can run 'gdk-pixbuf-query-loaders' here instead
in every boot of the system
|
| | | |
|
| | |
| |
| |
| |
| | |
This is needed by modern versions of xserver and GTK+
Put it in here until we upgrade the xserver to avoid rebuilds
|
| |\ \
| | |
| | |
| | |
| | | |
Reviewed-By: Pedro Alvarez <pedro.alvarez@codethink.co.uk>
Reviewed-By: Richard Dale <richard.dale@codethink.co.uk>
|
| |/ /
| |
| |
| | |
This means we use the out-of-tree module located in extra/
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | | |
Reviewed-By: Richard Maw <richard.maw@codethink.co.uk>
Reviewed-By: Paul Sherwood <paul.sherwood@codethink.co.uk>
|
| | | |
| | |
| | |
| | |
| | |
| | | |
If none of the MASON_ options are set then mason.configure will now do
nothing, instead of raising an error. This is needed because
mason.configure is enabled by default in the build-system.
|
| |/ /
| |
| |
| |
| |
| |
| |
| | |
Previously if you enabled distbuild.configure but didn't set all of the
required variables, your deployment would fail. This has become much
more annoying with the introduction of the build-system family of
systems, which are indented to be suitable either as a local builder or
part of a distbuild network.
|
| | | |
|
| | | |
|
| |\ \
| |/
|/|
| |
| | |
Reviewed-By: Richard Maw <richard.maw@codethink.co.uk>
Reviewed-By: Sam Thursfield <sam.thursfield@codethink.co.uk>
|
| | |
| |
| |
| |
| |
| | |
This could be improved in future by combining the cluster morphology
with the existing one, and mason/mason-generator.sh being improved to
allow choice between OpenStack and KVM.
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| | |
This adds TEST_INFRASTRUCTURE_TYPE and OPENSTACK_NETWORK_ID to
mason.conf, as well as ending the confusion of using both
MASON_TEST_HOST and TEST_VM_HOST_SSH_URL to mean the same thing
in different places.
|
| | | |
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Testing currently involves building a Baserock devel system,
deploying it as a VM and testing that that deployed VM can
build Baserock successfully.
Originally Mason used scripts/release-test to do testing on
a kvm host. In this patch the bits needed to do testing on
an OpenStack host are provided.
The new scripts/release-test-os script is based on the old
scripts/release-test, and it uses `nova` to boot/delete/etc
images and instances on OpenStack.
The mason script, `mason.sh` is updated to optionally run
either scripts/release-test-os or scripts/release-test,
depending on whether TEST_INFRASTRUCTURE_TYPE is set to
'openstack' or 'kvmhost' in the Mason's mason.conf.
The `os.conf` file is sourced by `mason.sh`, and should
be updated to contain the relevant credentials and details
for the OpenStack tenancy to be used for test deployments.
When Mason creates a test OpenStack instance, there is
potential for a race condition depending on whether ssh
comes up before the cloud-init has finished resizing the
instance's disc. If morph running on the test instance
tries to build before the disc size is increased, it will
fail complaining of insufficient free space.
To eliminate this race, the cloud init script
`os-init-script` is passed to `nova boot`. This touches
a file after the disc is resized, which Mason checks for
before it runs a `morph build`.
The `os.conf` and `os-init-script` files must both be
placed in the Mason system's `/root/` directory before
the system is deployed. This should happen in the
`mason.configure` configuration extension.
The `mason.configure` configuration extension should also
be updated to handle adding two extra variables to the
`mason.conf` file. These are the aforementioned
TEST_INFRASTRUCTURE_TYPE and OPENSTACK_NETWORK_ID, which is
the ID for the configured OpenStack network that test
instances should use.
|
| | |
|
| | |
|
| |\
| |
| |
| |
| | |
Reviewed-By: Richard Maw <richard.maw@codethink.co.uk>
Reviewed-By: Daniel Silverstone <daniel.silverstone@codethink.co.uk>
|
| | |
| |
| |
| |
| |
| |
| | |
These strata used to be in all devel systems and were removed. The only
extra component that a system needs to be a Vagrant basebox is the
VirtualBox Guest Additions, which are in the virtualbox-guest-x86_64
stratum.
|
| | |
| |
| |
| |
| |
| |
| | |
These are dependencies of the Baserock Import tool. The import tool will
be added to the devel system later, in a separate branch.
This increases the size of an x86_32 devel system from 1.1GB to 1.2GB.
|
| | |
| |
| |
| |
| |
| |
| | |
The build-system is equivalent in functionality to the current
devel-system that we release, but this change allows us to add more
components to the devel-system without increasing the amount of bytes we
have to arrange and transfer when making a release.
|
| | |
| |
| |
| |
| | |
These take the place of the devel system chroots that we released
previously, and should be functionally equivalent.
|
| | |
| |
| |
| |
| |
| | |
The 'build' system is now the recommended way of building other systems,
with 'devel' being a larger variant of 'build' that may be useful when
doing development and integration, in addition to building and deployment.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
It's better to have one type of system that can do either distributed or
local builds than to have separate ones that must both be kept up to
date with changes.
The need for a separate 'distbuild' stratum went already:
commit 1a7fbedf56a4c7a6afb683851dde5d34bbb48b86
Author: Richard Maw <richard.maw@codethink.co.uk>
Date: Thu Oct 2 14:16:00 2014 +0000
Split morph out of tools
morph now contains distbuild and morph-cache-server, so the distbuild
stratum can go away, and anything that needs it can now use morph.
|
| |\ \
| | |
| | |
| | |
| | |
| | | |
Reviewed-By: Pedro Alvarez <pedro.alvarez@codethink.co.uk>
Reviewed-By: Richard Maw <richard.maw@codethink.co.uk>
Reviewed-By: Sam Thursfield <sam.thursfield@codethink.co.uk>
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
This partially reverts ced256bda95f184361815a6444d752ee10d86d02
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Reviewed-By: Adam Coldrick <adam.coldrick@codethink.co.uk>
Reviewed-By: Francisco Redondo Marchena <francisco.marchena@codethink.co.uk>
|
| | | | |
| | | |
| | | |
| | | | |
Various Gems require one or other of these tools at build time.
|
