all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 25953@debbugs.gnu.org
Subject: bug#25953: [PATCH] gnu: mesa: Build LLVM Gallium drivers.
Date: Fri, 10 Mar 2017 20:45:23 -0500	[thread overview]
Message-ID: <87o9x8powc.fsf@netris.org> (raw)
In-Reply-To: <87poht2p1w.fsf@elephly.net> (Ricardo Wurmus's message of "Tue, 07 Mar 2017 14:29:15 +0100")

Ricardo Wurmus <rekado@elephly.net> writes:

> Mark H Weaver <mhw@netris.org> writes:
>
>> Ricardo Wurmus <rekado@elephly.net> writes:
>>
>>> Fixes <https://bugs.gnu.org/25953>.
>>>
>>> * gnu/packages/gl.scm (mesa)[inputs]: Add llvm.
>>> [arguments]: Build LLVM Gallium drivers.
>>
>> I'm uncomfortable adding llvm as a requirement for our most minimal X11
>> system, for several reasons.  Can we find a way to make this optional?
>
> Would it make sense to add a “mesa-minimal” package and a minimal
> variant of xorg-server where any mesa package is rewritten to be
> mesa-minimal?

Judging by the number of packages that include 'mesa' as an input, it
won't be so easy.  Search for ",mesa" in gnu/packages/*.scm, and see the
output of "guix refresh -l mesa".  The xf86-video-* packages include
'mesa' as input, and many other packages as well.

I won't block this, but I will take this opportunity to mention that for
those of us who wish to build GuixSD from source code on our own
machines, life is becoming increasingly uncomfortable as more and more
optional features are added to our core packages.  We are on a
trajectory to leave that set of users behind, as we cater primarily to
the majority who use the latest Intel machines and don't worry about the
security of either the Intel Management Engine or our build farm.

       Mark

  reply	other threads:[~2017-03-11  1:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-03  8:04 bug#25953: [Mesa] Very low Gallium performance compared to Trisquel Matthew Brooks
2017-03-03 17:53 ` Leo Famulari
2017-03-03 18:15   ` Marius Bakke
     [not found]     ` <CAPi-ftoekP+QWmy=BRyKJr5YWpkwK0eFu0KmCHfxwZC78sJTjA@mail.gmail.com>
2017-03-03 22:22       ` bug#25953: Fwd: " Matthew Brooks
2017-03-06 14:35     ` bug#25953: [PATCH] gnu: mesa: Build LLVM Gallium drivers Ricardo Wurmus
2017-03-06 14:58       ` Thompson, David
2017-03-06 16:46         ` Danny Milosavljevic
2017-03-06 18:55         ` Leo Famulari
2017-03-06 21:37           ` Ricardo Wurmus
2017-03-07  7:04       ` Mark H Weaver
2017-03-07 13:29         ` Ricardo Wurmus
2017-03-11  1:45           ` Mark H Weaver [this message]
2017-03-11 10:58             ` Ludovic Courtès
     [not found]             ` <CAPi-ftq3D390s1vV1Oqagf5ut=XGeAEdrU6a_T5Q973wzMniPA@mail.gmail.com>
2017-03-15  8:58               ` Matthew Brooks
2017-03-15 11:58                 ` Ricardo Wurmus

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87o9x8powc.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=25953@debbugs.gnu.org \
    --cc=rekado@elephly.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.