public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: virtual/tmpfiles/
Date: Thu, 15 Jun 2023 02:07:24 +0000 (UTC)	[thread overview]
Message-ID: <1686794805.dd9f1217aada80b4e25327638e3f8ceacf666eb3.sam@gentoo> (raw)

commit:     dd9f1217aada80b4e25327638e3f8ceacf666eb3
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Thu Jun 15 02:06:17 2023 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Thu Jun 15 02:06:45 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=dd9f1217

virtual/tmpfiles: add USE=systemd to help dependency resolution

Portage sometimes struggles when moving between OpenRC <-> systemd and ends up
wasting cycles.

Give it a hint like we do in virtual/libudev.

Signed-off-by: Sam James <sam <AT> gentoo.org>

 .../tmpfiles/{tmpfiles-0-r4.ebuild => tmpfiles-0-r5.ebuild}  | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/virtual/tmpfiles/tmpfiles-0-r4.ebuild b/virtual/tmpfiles/tmpfiles-0-r5.ebuild
similarity index 78%
rename from virtual/tmpfiles/tmpfiles-0-r4.ebuild
rename to virtual/tmpfiles/tmpfiles-0-r5.ebuild
index ed8a8b1c5b01..2d31b47c699d 100644
--- a/virtual/tmpfiles/tmpfiles-0-r4.ebuild
+++ b/virtual/tmpfiles/tmpfiles-0-r5.ebuild
@@ -1,16 +1,16 @@
 # Copyright 1999-2023 Gentoo Authors
 # Distributed under the terms of the GNU General Public License v2
 
-EAPI=7
+EAPI=8
 
 DESCRIPTION="Virtual to select between different tmpfiles.d handlers"
 SLOT="0"
 KEYWORDS="~alpha amd64 arm arm64 hppa ~ia64 ~loong ~m68k ~mips ppc ppc64 ~riscv ~s390 sparc x86 ~amd64-linux ~x86-linux ~arm64-macos ~ppc-macos ~x64-macos ~x64-solaris"
+IUSE="systemd"
 
 RDEPEND="
 	!prefix-guest? (
-		|| (
-			sys-apps/systemd-utils[tmpfiles]
-			sys-apps/systemd
-		)
-	)"
+		systemd? ( sys-apps/systemd )
+		!systemd? ( sys-apps/systemd-utils[tmpfiles] )
+	)
+"


             reply	other threads:[~2023-06-15  2:07 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-15  2:07 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-06-15  2:03 [gentoo-commits] repo/gentoo:master commit in: virtual/tmpfiles/ Sam James
2023-04-22 12:08 Sam James
2022-08-04 21:56 David Seifert
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-24 11:33 Fabian Groffen
2021-05-13 15:19 David Seifert
2021-01-06 12:42 Fabian Groffen
2020-12-03 11:32 Andreas K. Hüttel
2020-11-28 19:15 Georgy Yakovlev
2020-11-28 19:15 Georgy Yakovlev
2020-10-29  6:42 Georgy Yakovlev
2019-05-04  9:37 Mikle Kolyada
2018-12-07  9:01 Fabian Groffen
2018-07-04 14:08 Michael Haubenwallner
2018-02-22 20:49 Michał Górny
2017-04-08  8:58 Jeroen Roovers
2017-03-11 17:07 Agostino Sarubbo
2017-02-28 11:22 Tobias Klausmann
2017-02-25 10:03 Agostino Sarubbo
2017-02-24  8:30 Michael Weber
2017-02-24  5:45 Mike Frysinger
2017-02-22 16:08 Agostino Sarubbo
2017-02-22 15:06 Agostino Sarubbo
2016-12-01 22:18 William Hubbs

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=1686794805.dd9f1217aada80b4e25327638e3f8ceacf666eb3.sam@gentoo \
    --to=sam@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