From: Julien Lepiller <julien@lepiller.eu>
To: "Ludovic Courtès" <ludo@gnu.org>, "Lars-Dominik Braun" <lars@6xq.net>
Cc: guix-devel@gnu.org
Subject: Re: eudev deprecation
Date: Tue, 28 Sep 2021 10:12:28 -0400 [thread overview]
Message-ID: <0AC9BB58-F379-4928-AD38-6B279F442D91@lepiller.eu> (raw)
In-Reply-To: <87v92kdi65.fsf@gnu.org>
Le 28 septembre 2021 08:00:02 GMT-04:00, "Ludovic Courtès" <ludo@gnu.org> a écrit :
>Hi,
>
>Lars-Dominik Braun <lars@6xq.net> skribis:
>
>> it looks like eudev, which we heavily rely on, is dead upstream:
>> https://github.com/gentoo/eudev/issues/199
>>
>> Looking at Gentoo’s ebuilds it should be possible to “extract”
>> and build udev from systemd’s sources.
>
>Good. That’s essentially what eudev is.
>
>Tobias Geerinckx-Rice <me@tobias.gr> skribis:
>
>> Further update:
>>
>>> ADOPTION NOTICE (2021-09-14)
>>> Currently eudev is in the process of being adopted by a newly
>>> formed project by Alpine, Devuan and Gentoo contributors [...]
>>
>> -- https://github.com/eudev-project/eudev
>>
>> We'll see? Talk and Git repos are cheap; actually putting in this
>> work is not.
>
>Interesting.
>
>Julien mentioned on IRC that Linux From Scratch is also considering
>switching. Julien, what’s the takeaway from the LFS discussions so far?
>
>Thanks,
>Ludo’.
My understandeng is that LFS will use udev, directly extracted fsom systemd's sources, in its sysvinit version. See https://wiki.linuxfromscratch.org/lfs/ticket/4914 for reference.
prev parent reply other threads:[~2021-09-29 0:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-12 9:44 eudev deprecation Lars-Dominik Braun
2021-09-12 9:54 ` Tobias Geerinckx-Rice
2021-09-12 9:57 ` Tobias Geerinckx-Rice
2021-09-12 10:04 ` Tobias Geerinckx-Rice
2021-09-16 20:56 ` Tobias Geerinckx-Rice
2021-09-28 12:00 ` Ludovic Courtès
2021-09-28 14:12 ` Julien Lepiller [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=0AC9BB58-F379-4928-AD38-6B279F442D91@lepiller.eu \
--to=julien@lepiller.eu \
--cc=guix-devel@gnu.org \
--cc=lars@6xq.net \
--cc=ludo@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).