Improving Our Docs

Robert Ancell robert.ancell at canonical.com
Tue Jul 2 05:14:55 UTC 2013


Hi Jeff,

On Sat, Jun 22, 2013 at 5:20 AM, Jeff Spaleta <jspaleta at fedoraproject.org>wrote:

> Morning,
>
> For starters to smoke test Mir I need:
> The... canonical...set of branches for Mir and its dependencies as
> used in current Mir development workflow necessary to smoke test a
> binary mir in a locally controlled clean build environment
> (/usr/local) so that I can use environment variables to switch from
> the environment provided dependencies to the mir specific dependencies
> if the environment does not provide them.  Current build from source
> and test implicitly assumes you are going to pull patched deps from
> ppa staging which implicitly assumes a very specific environment thus

a non-starter for anyone not using that environment.
>

I figure you have them, but for an official statement to the list the
branches you need are:

1. lp:mir
2. lp:unity-system-compositor
3. lp:~mir-team/lightdm/unity [1]
4. https://github.com/RAOF/mesa branch egl-platform-mir
5. https://github.com/RAOF/xserver branch vladmir

1 and 2 are CMake and 3, 4 and 5 are autotools. So they should in theory
work fine in /usr/local though it's probably not well tested.

Dependencies are specified in the build systems for each and as far as I
know don't require anything non-standard over what their upstreams provide.

--Robert

[1] Though I have just merged the main portion of this into lp:lightdm,
it's probably safer to use the ~mir-team branch at this point in time.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/mir-devel/attachments/20130702/049ee1f3/attachment.html>


More information about the Mir-devel mailing list