Re: [PATCH 06/10] gnu: mesa: Enable wayland support.

On Sat, Aug 06, 2016 at 11:01:43PM -0400, Leo Famulari wrote: > On Fri, Aug 05, 2016 at 04:31:25PM +0200, David Craven wrote: > > So now that 0.11.0 was merged can the update to mesa 12.0.0 go into > > core-updates? > > We need to make the new core-updates branch, but there is a hiccup: > >

Re: [PATCH 06/10] gnu: mesa: Enable wayland support.

On Fri, Aug 05, 2016 at 04:31:25PM +0200, David Craven wrote: > So now that 0.11.0 was merged can the update to mesa 12.0.0 go into > core-updates? We need to make the new core-updates branch, but there is a hiccup: http://lists.gnu.org/archive/html/guix-devel/2016-08/msg00456.html Please hold

Re: [PATCH 06/10] gnu: mesa: Enable wayland support.

So now that 0.11.0 was merged can the update to mesa 12.0.0 go into core-updates?

Re: [PATCH 06/10] gnu: mesa: Enable wayland support.

David Craven skribis: >> What did ‘guix size’ reveal, and what does it suggest? :-) I wrote “go for it”, but I should have added “not now”. :-) Mesa has 467 dependents, which we cannot afford to rebuild at the moment. Could you keep it on hold? Thanks, Ludo’.

Re: [PATCH 06/10] gnu: mesa: Enable wayland support.

David Craven skribis: >> What did ‘guix size’ reveal, and what does it suggest? :-) > > Efraim did an estimate of about 10 MB, my measurement was 30MB but > that includes the spirv toolchain and virtio driver. Comparing ‘guix size mesa’ to ‘guix size mesa wayland’ shows a 6%

Re: [PATCH 06/10] gnu: mesa: Enable wayland support.

> What did ‘guix size’ reveal, and what does it suggest? :-) Efraim did an estimate of about 10 MB, my measurement was 30MB but that includes the spirv toolchain and virtio driver. Are these boundaries measurements close enough for a decision? I can do a more precise measurement if you want... I

Re: [PATCH 06/10] gnu: mesa: Enable wayland support.

David Craven skribis: > So is this going into the main mesa package? Or should I submit a > mesa-wayland package instead? (Please keep a bit of context when replying.) In my last message I gave you the main criterion for deciding whether to add Wayland support in Mesa so that

Re: [PATCH 06/10] gnu: mesa: Enable wayland support.

So is this going into the main mesa package? Or should I submit a mesa-wayland package instead?

Re: [PATCH 06/10] gnu: mesa: Enable wayland support.

Ah I'm still rebuilding after a rebase, that's probably the issue then.

Re: [PATCH 06/10] gnu: mesa: Enable wayland support.

David Craven skribis: > When trying to run guix size on a custom built package I get a no > substitue information available message... Quoting the manual: When the package passed to ‘guix size’ is available in the store, ‘guix size’ queries the daemon to determine its

Re: [PATCH 06/10] gnu: mesa: Enable wayland support.

On Thu, Jul 21, 2016 at 03:29:37PM +0300, Efraim Flashner wrote: > On Thu, Jul 21, 2016 at 02:19:26PM +0200, David Craven wrote: > > When trying to run guix size on a custom built package I get a no > > substitue information available message... > > > > You're going to have to build it first

Re: [PATCH 06/10] gnu: mesa: Enable wayland support.

On Thu, Jul 21, 2016 at 02:19:26PM +0200, David Craven wrote: > When trying to run guix size on a custom built package I get a no > substitue information available message... > You're going to have to build it first both ways, once with and once without the wayland support. -- Efraim Flashner

Re: [PATCH 06/10] gnu: mesa: Enable wayland support.

When trying to run guix size on a custom built package I get a no substitue information available message... David

Re: [PATCH 06/10] gnu: mesa: Enable wayland support.

Hi! David Craven skribis: > Sounds good. Just wondering what's the policy on default build options > in guixsd? Leaning more towards enable everything than enable as > little as possible? Or do you decide on a case by case basis? Just > curious... It’s mostly on a case-by-case

Re: [PATCH 06/10] gnu: mesa: Enable wayland support.

Sounds good. Just wondering what's the policy on default build options in guixsd? Leaning more towards enable everything than enable as little as possible? Or do you decide on a case by case basis? Just curious...

Re: [PATCH 06/10] gnu: mesa: Enable wayland support.

David Craven skribis: > * gnu/packages/gl.scm (mesa): Enable configure-flags required by wayland. This patch and the other patches that touch libdrm and mesa look good but… they trigger a lot of rebuild, so we need to “schedule” them. Currently the build farm is a bit

[PATCH 06/10] gnu: mesa: Enable wayland support.

* gnu/packages/gl.scm (mesa): Enable configure-flags required by wayland. --- gnu/packages/gl.scm | 9 +++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/gnu/packages/gl.scm b/gnu/packages/gl.scm index 6e635a3..67bab1b 100644 --- a/gnu/packages/gl.scm +++