unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Efraim Flashner <efraim@flashner.co.il>
Cc: guix-devel@gnu.org
Subject: Re: 03/03: gnu: libinput: Update to 1.9.3.
Date: Mon, 11 Dec 2017 10:33:23 +0100	[thread overview]
Message-ID: <87o9n54nj0.fsf@gnu.org> (raw)
In-Reply-To: <20171210111154.GE23558@macbook41> (Efraim Flashner's message of "Sun, 10 Dec 2017 13:11:54 +0200")

Hi,

Efraim Flashner <efraim@flashner.co.il> skribis:

> On Fri, Dec 08, 2017 at 08:36:27PM -0500, Mark H Weaver wrote:
>> efraim@flashner.co.il (Efraim Flashner) writes:
>> 
>> > efraim pushed a commit to branch master
>> > in repository guix.
>> >
>> > commit 5f5083749c1ff2731e84fa7d8eea182ad45c18a5
>> > Author: Efraim Flashner <efraim@flashner.co.il>
>> > Date:   Fri Dec 8 09:25:40 2017 +0200
>> >
>> >     gnu: libinput: Update to 1.9.3.
>> >     
>> >     * gnu/packages/freedesktop.scm (libinput): Update to 1.9.3.
>> >     [build-system]: Switch to meson-build-system.
>> 
>> FYI, switching to 'meson-build-system' here caused around 120+ more
>> dependency failures on armhf-linux, including xf86-input-libinput, since
>> we've never successfully built 'ninja' on armhf-linux.  So, we've
>> essentially just lost graphics support on armhf-linux.
>> 
>>        Mark
>
> 1.8.3 is the last version that still has autotools support, it was
> removed in the 1.9 branch. Unfortunately I don't have access to an armhf
> machine to try to fix the armhf build of ninja. I suspect that this is
> going to be an issue going forward, as more packages move to a meson
> build system.
>
> I'm not against downgrading to 1.8.3 in the mean time to keep the
> packages that depend on libinput{,-minimal} available to armhf users,
> but it is something that's going to need to be addressed sooner rather
> than later.

Maybe the safe approach is to revert now so armhf users get graphics
back, take time to investigate and fix the Ninja build failures on ARM
(surely there are patches floating around on the intertubes), and then
reinstate the upgrade.

How does that sound?

(Note that I’m volunteering, but hey!  ;-))

Ludo’.

      reply	other threads:[~2017-12-11  9:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20171208073200.21170.44618@vcs0.savannah.gnu.org>
     [not found] ` <20171208073201.5821F204F4@vcs0.savannah.gnu.org>
2017-12-09  1:36   ` 03/03: gnu: libinput: Update to 1.9.3 Mark H Weaver
2017-12-10 11:11     ` Efraim Flashner
2017-12-11  9:33       ` Ludovic Courtès [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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=87o9n54nj0.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=efraim@flashner.co.il \
    --cc=guix-devel@gnu.org \
    /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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).