| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
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: Sam Thursfield <sam.thursfield@codethink.co.uk>
|
| |
| |
| |
| |
| | |
It had lots of unneccessary stuff and wouldn't build.
Have removed unneccessary stuff; is now just base system plus node.
|
|\ \
| | |
| | |
| | |
| | | |
Reviewed-By: James Thomas <james.thomas@codethink.co.uk>
Reviewed-By: Sam Thursfield <sam.thursfield@codethink.co.uk>
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In this way we can build completely wayland-only systems
The reason to do this is that cairo will pull the X11 dependency if the
mesa stratum is built with X11 support (as graphics-common depens on
mesa-common)
|
| | |
| | |
| | |
| | |
| | | |
As libdrm was moved to an independent stratum this only holds
some macros needed to compile other strata
|
| | |
| | |
| | |
| | | |
So libdrm only gets build when it's really needed
|
| |/
| |
| |
| | |
With basic infrastructure components like libdrm and xorg macros
|
| | |
|
| | |
|
|/ |
|
|\
| |
| |
| |
| | |
Reviewed-By: Richard Maw <richard.maw@codethink.co.uk>
Reviewed-By: Sam Thursfield <sam.thursfield@codethink.co.uk>
|
| | |
|
|/ |
|
|\
| |
| |
| |
| |
| | |
'origin/baserock/ps/cycle-refuses-to-delete-TEST-system'
Reviewed-by: Richard Maw (+2)
|
| | |
|
|\ \
| |/
|/|
| |
| |
| | |
Change-Id: I96d767050b7261cb9e4ec1ff6ce8fa1865bf51ab
Reviewed-by: Sam Thursfield <sam.thursfield@codethink.co.uk>
Reviewed-by: Pedro Alvarez <pedro.alvarez@codethink.co.uk>
|
|/
|
|
| |
Change-Id: I1f77fc4c23335f838f1b1f4b4ddaa8da355dab8f
|
|\
| |
| |
| |
| | |
Reviewed-By: Paul Sherwood <paul.sherwood@codethink.co.uk>
Reviewed-By: Richard Maw <richard.maw@gmail.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
--disable-assertions: those checks are not needed in production systems
--enable-optimized: it will help compiling on ARM
--enable-shared: mesa recommends llvm to be compiled in this way
--enable-targets=host: Only build for the host architecture
See http://llvm.org/docs/GettingStarted.html#local-llvm-configuration and
http://llvm.org/docs/HowToBuildOnARM.html
|
| |
| |
| |
| | |
Seems 3.4.2 and 3.5.1 doesnt compile in ARM
|
| |
| |
| |
| |
| | |
llvm is a bif piece of software that take long time to build
With this move we will only build it when its really necessary
|
| | |
|
|\ \
| | |
| | |
| | | |
This updates morph and ensures the new dependencies are available.
|
| | |
| | |
| | |
| | |
| | | |
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: Richard Maw
Reviewed-by: Sam Thursfield
Reviewed-by: Francisco Redondo Marchena
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Some users think that adding the cloud-init configuration
extension to a system is enough to install and enable cloud-init.
This is not true, to add and enable cloud-init in a system the
system has to have cloud-init installed (cloud-init chunk) and
cloud-init services have to be enabled (with cloud-init
configuration extension)
This patch is to alert the user that cloud-init can't be enabled
in a system without cloud-init installed, and making the
deployment fail.
|
|\ \ \
| |_|/
|/| |
| | |
| | | |
Reviewed-By: Richard Ipsum (on IRC)
Reviewed-By: Francisco Redondo Marchena (on IRC)
|
|/ / |
|
|\ \
| | |
| | |
| | |
| | | |
Reviewed-By: Pedro Alvarez <pedro.alvarez@codethink.co.uk>
Reviewed-By: Paul Sherwood <paul.sherwood@codethink.co.uk>
|
| | |
| | |
| | |
| | | |
The mason.configure extension is also added to each system.
|
|\ \ \
| |/ /
|/| |
| | |
| | |
| | | |
Reviewed by:
Sam Thursfield
Paul Sherwood
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
|/ / |
|
| |
| |
| |
| |
| | |
Reviewed-by: Paul Sherwood
Reviewed-by: Sam Thursfield
|
| |
| |
| |
| |
| | |
Reviewed-by: Daniel Silverstone
Reviewed-by: Paul Sherwood
|
|\ \
| | |
| | |
| | |
| | | |
Reviewed-By: Adam Coldrick <adam.coldrick@codethink.co.uk>
Reviewed-By: Sam Thursfield <sam.thursfield@codethink.co.uk>
|
| | | |
|