Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Romain Naour <romain.naour@smile.fr>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/2] package/phython-libevdev: new package
Date: Wed, 24 Aug 2022 12:13:58 +0200	[thread overview]
Message-ID: <20220824121358.4650be85@windsurf> (raw)
In-Reply-To: <20220809132730.232111-1-romain.naour@smile.fr>

On Tue,  9 Aug 2022 15:27:29 +0200
Romain Naour <romain.naour@smile.fr> wrote:

> python-libevdev is needed for libinput replay command:
> 
> $ libinput replay recording.yml
> Error: No module named 'libevdev'
> One or more python modules are missing. Please install those modules and re-run this tool.
> 
> Indeed only libinput-replay tool is a python script
> (like libinput-analyze-recording, libinput-measure-fuzz...)
> 
> phython-libevdev itself requires a kernel built with
> CONFIG_INPUT_UINPUT option enabled, enable this option
> if a kernel is built by Buildroot.
> 
> Signed-off-by: Romain Naour <romain.naour@smile.fr>
> ---
>  DEVELOPERS                                   |  1 +
>  package/Config.in                            |  1 +
>  package/python-libevdev/Config.in            |  7 +++++++
>  package/python-libevdev/python-libevdev.hash |  5 +++++
>  package/python-libevdev/python-libevdev.mk   | 20 ++++++++++++++++++++
>  5 files changed, 34 insertions(+)
>  create mode 100644 package/python-libevdev/Config.in
>  create mode 100644 package/python-libevdev/python-libevdev.hash
>  create mode 100644 package/python-libevdev/python-libevdev.mk

So, I have applied both patches, but I had to split things up:

 * From PATCH 2/2, I took the removal of the Python tools, made it
   unconditional, and applied that to master.

 * In next, I cherry-picked the patch from master that unconditionally
   removes Python tools of libinput, then applied the python-libevdev
   patch, then applied a patch that adds the libinput option for Python
   tools.

This way, we have the fix in master (removal of Python tools) and the
new feature in next.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2022-08-24 10:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-09 13:27 [Buildroot] [PATCH 1/2] package/phython-libevdev: new package Romain Naour
2022-08-09 13:27 ` [Buildroot] [PATCH 2/2] package/libinput: remove python tools scripts if python is missing Romain Naour
2022-08-24 10:13 ` Thomas Petazzoni via buildroot [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=20220824121358.4650be85@windsurf \
    --to=buildroot@buildroot.org \
    --cc=romain.naour@smile.fr \
    --cc=thomas.petazzoni@bootlin.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox