Subject: Building Mir Debian packages

From: Robert Ancell <[email-masked]>
Date: Thu, 21 Mar 2013 20:49:42 +1300

Hi,

Everyone might know this but I though it is worth mentioning to remember
about the Debian packaging when making changes to Mir. If you change
things you may need to test that the packaging still compiles. This is
just a matter of running:

$ debuild

>From the toplevel Mir directory. Jenkins does do this but you probably
want to know before proposing if you're moving/renaming installed files.
The downside is debuild will compile Mir from scratch so it's a bit time
consuming.

--Robert

---

From: Thomas Voß <[email-masked]>
Date: Thu, 21 Mar 2013 13:27:28 +0100

> The downside is debuild will compile Mir from scratch so it's a bit time

+1, the Mir CMake setup contains some targets to help developers for
these use-cases, most notably:

	- pre-push: distills a source tarball from the working copy and builds
and tests Mir in a chroot.

hth,

  Thomas

---

From: Bryce Harrington <[email-masked]>
Date: Thu, 21 Mar 2013 13:38:23 -0700

> and tests Mir in a chroot.

Thanks for the tip.  I found that make pre-push didn't work, and made a
guess at the fix:

  https://code.launchpad.net/~bryce/mir/mir-debuild-fixes 

debuild also failed, and the branch includes a change to address that.

A sanity check would be welcomed.  I plan to propose it for merging
after my mir-apport-hook branch I just now posted.

Bryce