public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "William Hubbs" <williamh@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: virtual/udev/
Date: Thu, 22 Jul 2021 22:45:11 +0000 (UTC)	[thread overview]
Message-ID: <1626993819.4aeb78f44974da73e2c819a1ad0a300df885e025.williamh@gentoo> (raw)

commit:     4aeb78f44974da73e2c819a1ad0a300df885e025
Author:     William Hubbs <williamh <AT> gentoo <DOT> org>
AuthorDate: Thu Jul 22 22:43:18 2021 +0000
Commit:     William Hubbs <williamh <AT> gentoo <DOT> org>
CommitDate: Thu Jul 22 22:43:39 2021 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4aeb78f4

virtual/udev: 249 bump to prefer sys-fs/udev over sys-fs/eudev

This is being done because sys-fs/eudev is unmaintained (its author would
prefer it go away, but it remains for non-glibc targets like musl) and
sys-fs/udev doesn't require systemd - it is standalone.

Package-Manager: Portage-3.0.20, Repoman-3.0.2
Signed-off-by: William Hubbs <williamh <AT> gentoo.org>

 virtual/udev/udev-249.ebuild | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)

diff --git a/virtual/udev/udev-249.ebuild b/virtual/udev/udev-249.ebuild
new file mode 100644
index 00000000000..f328c36934e
--- /dev/null
+++ b/virtual/udev/udev-249.ebuild
@@ -0,0 +1,16 @@
+# Copyright 1999-2021 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=7
+
+DESCRIPTION="Virtual to select between different udev daemon providers"
+SLOT="0"
+KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~hppa ~ia64 ~m68k ~mips ~ppc ~ppc64 ~riscv ~s390 ~sparc ~x86"
+
+RDEPEND="
+	|| (
+		>=sys-fs/udev-249
+		>=sys-fs/eudev-2.1.1
+		>=sys-apps/systemd-249
+	)
+"


             reply	other threads:[~2021-07-22 22:45 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-22 22:45 William Hubbs [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-10-12 14:27 [gentoo-commits] repo/gentoo:master commit in: virtual/udev/ Mike Gilbert
2023-10-12 14:27 Mike Gilbert
2023-06-15  2:03 Sam James
2023-06-15  2:03 Sam James
2023-06-15  2:03 Sam James
2022-06-04  2:21 Sam James
2022-06-03  7:05 Sam James
2022-06-03  0:52 Sam James
2022-06-03  0:52 Sam James
2022-06-03  0:37 Sam James
2022-06-02  1:52 Sam James
2022-06-02  1:52 Sam James
2022-05-30  7:15 Sam James
2022-04-17 12:48 Sam James
2022-04-16 23:13 Mike Gilbert
2021-08-13 16:18 Mike Gilbert
2021-08-09 15:15 Mike Gilbert
2021-05-13 15:19 David Seifert
2020-11-18  8:47 Michał Górny
2020-11-17 19:05 Agostino Sarubbo
2020-11-01 11:12 Sam James
2020-10-28 16:18 Sam James
2020-10-26 23:51 Sergei Trofimovich
2020-10-26 23:49 Sergei Trofimovich
2020-10-26 23:47 Sergei Trofimovich
2020-10-26 23:44 Sergei Trofimovich
2020-10-26  0:15 Sam James
2020-10-25 21:34 Thomas Deutschmann
2020-10-05  2:45 Michał Górny
2020-10-04 21:17 Michał Górny
2019-05-04 20:17 Andreas K. Hüttel
2018-01-13  6:51 Mike Frysinger
2017-03-21  9:50 Jeroen Roovers
2017-02-28 11:22 Tobias Klausmann
2017-02-25 10:03 Agostino Sarubbo
2017-02-24 13:38 Agostino Sarubbo
2017-02-24 13:20 Agostino Sarubbo
2017-02-24  8:30 Michael Weber
2016-03-01 18:10 Patrick Lauer

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=1626993819.4aeb78f44974da73e2c819a1ad0a300df885e025.williamh@gentoo \
    --to=williamh@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox