mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: Christian Melki <christian.melki@t2data.com>
Cc: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>,
	Mariusz Pielat <mariusz.pielat@gmail.com>
Subject: Re: [ptxdist] Reporting difficulties to build usbutils package, RFC EUDEV?
Date: Fri, 19 Jan 2024 12:27:04 +0100	[thread overview]
Message-ID: <ZapciGr8w3gjZ5WO@pengutronix.de> (raw)
In-Reply-To: <bb56a1e8-cd8e-4ec7-8069-d60b22834168@t2data.com>

On Sat, Jan 13, 2024 at 08:56:17PM +0100, Christian Melki wrote:
> On 1/13/24 08:22, Mariusz Pielat wrote:
> > I've tried to enable and build the usbutils package in PTXDIST-2023.07.0
> > and it was not possible due to unfulfilled requirements. 
> > 
> > In the given PTXDIST version the usbutils rulefile points to version
> > 015. According to usbutils/configure.ac <http://configure.ac> it
> > requires libudev in version 196 or higher
> > (https://github.com/gregkh/usbutils/blob/v015/configure.ac#L20
> > <https://github.com/gregkh/usbutils/blob/v015/configure.ac#L20>).
> > PTXDIST rulefile for the udev package points to version 182, so it's
> > lower than required.
> > 
> > I can see that the problem exists for newer PTXDIST versions as well. 
> > 
> > So far I didn't work on that issue - just reporting.
> > 
> 
> Hi,
> 
> Thanks for reporting. I think this has been missed for a long time, the
> blame line for version 196 claims it's 11 years old...
> usbutils seem to use it for the hwdb implementation.
> 
> This hasn't triggered because I think most targets are systemd based.
> And that hwdb implementation should work fine. I have locally been
> running eudev instead of udev as a drop in replacement for ages. And
> that one works fine too.
> 
> I think the correct solution here is to use eudev (which is actively
> developed still) and drop udev-182 (12 something years old by now?) or
> just drop legacy builds without systemd altogether.

I think it should also be possible to just install the new udev from the
current systemd sources without systemd itself. But such an update needs to
be done by someone who actually uses that. For many years now I've only had
projects that use systemd.

Regards,
Michael

> I'm not really a fan of the latter, but the argument against it
> increases as time passes by.
> 
> I could post the eudev drop in replacement bump (probably needs some
> more work), but I'm unsure if people in general thinks it's worth the
> hassle.
> 
> Regards,
> Christian
> 
> > Best Regards,
> > Mariusz
> > 
> 
> 
> 

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |



      reply	other threads:[~2024-01-19 11:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAF12Fw=HyNHrqv1J_4Ct2PkrHV4jne5VEkHs5tM2WPCMZGx2cQ@mail.gmail.com>
2024-01-13 19:56 ` Christian Melki
2024-01-19 11:27   ` Michael Olbrich [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=ZapciGr8w3gjZ5WO@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=christian.melki@t2data.com \
    --cc=mariusz.pielat@gmail.com \
    --cc=ptxdist@pengutronix.de \
    /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