all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Rutger Helling <rhelling@mykolab.com>
To: Marius Bakke <mbakke@fastmail.com>
Cc: 29625-done@debbugs.gnu.org
Subject: [bug#29625] [PATCH core-updates] Vulkan patch series.
Date: Mon, 18 Dec 2017 13:24:53 +0100	[thread overview]
Message-ID: <ae1d68b67df1d2365c478fcc88e51ecb@mykolab.com> (raw)
In-Reply-To: <87a7yg6xjs.fsf@fastmail.com>

Thanks for clarifying!

I guess this is just a heads-up then that adding python2-mako to 
native-inputs is likely enough to make 17.3.1 work, whenever that comes 
out :).

On 2017-12-18 13:16, Marius Bakke wrote:

> Rutger Helling <rhelling@mykolab.com> writes:
> 
>> Hey Marius,
>> 
>> Thanks a lot for improving and fixing the patches!
>> 
>> Regarding your questions; when I tried to build the Vulkan drivers on
>> Mesa on i686 it failed to build.
>> I figured it was better to just leave it at x86_86 for now. In a 
>> future
>> core-updates cycle it might be a good idea to start looking into other
>> architectures.
>> 
>> Retroarch won't be affected if your hardware doesn't support Vulkan, 
>> it
>> defaults to OpenGL anyway. It's just a setting you can modify
>> (video_driver).
> 
> OK, thanks for confirming.
> 
>> I also had an unrelated question. I saw that you updated Mesa to 
>> 17.2.7.
>> I'm running 17.3.0 myself right now.
>> Is it customary in Guix to wait for the first point release, or do you
>> want me to send in a patch?
>> It really only consists of updating the version, checksum and adding a
>> native-input python2-mako.
> 
> The Mesa release notes[0] has this blurb when the minor version 
> changes:
> 
> Mesa 17.3.0 is a new development release. People who are concerned with
> stability and reliability should stick with a previous release or wait
> for Mesa 17.3.1.
> 
> Since we will be "stuck" on this Mesa version for some time, I prefer
> sticking to the stable branches.  17.2.7 is also newer than 17.3.0 :-)
> 
> [0] https://www.mesa3d.org/relnotes/17.3.0.html

      reply	other threads:[~2017-12-18 12:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-09 13:54 [bug#29625] [PATCH core-updates] Vulkan patch series Rutger Helling
2017-12-10 10:41 ` Rutger Helling
2017-12-13 18:30 ` Marius Bakke
2017-12-14 22:26   ` Rutger Helling
2017-12-18  0:26     ` bug#29625: " Marius Bakke
2017-12-18  9:10       ` [bug#29625] " Rutger Helling
2017-12-18 12:16         ` Marius Bakke
2017-12-18 12:24           ` Rutger Helling [this message]

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=ae1d68b67df1d2365c478fcc88e51ecb@mykolab.com \
    --to=rhelling@mykolab.com \
    --cc=29625-done@debbugs.gnu.org \
    --cc=mbakke@fastmail.com \
    /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.