From: Mitchell Dorrell <mwd@psc.edu>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] --depclean and openrc [Was: Wayland! Beware of!]
Date: Thu, 26 Sep 2024 20:09:39 -0400 [thread overview]
Message-ID: <CAHqckJ2-88EX9eeVJZ53kM4dKLMGwmt5LPROXsV_vVxEZB42rw@mail.gmail.com> (raw)
In-Reply-To: <8634lp1dpy.fsf@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1184 bytes --]
On Tue, Sep 24, 2024, 07:41 Arsen Arsenović <arsen@gentoo.org> wrote:
> I do wonder if we should keep s6, runit and daemontools in that virutal
> though, given that we can't boot them. Perhaps they'd be fine behind a
> USE flag. I'll propose that.
>
So, this is a case where you definitely always need one of the
dependencies, and sometimes you might want two, but the reason you might
want the second one would not be to fulfill the purpose represented by the
virtual.
It sounds to me like a set of local USE flags would be perfect, with a
REQUIRED_USE enforcing exactly-one-of to choose the dependency. The USE
flag controls the choice, and if you pull in an alternative service manager
for an unrelated reason, it doesn't change the USE flag, so it doesn't
change the dependency which satisfies the virtual. The USE-disabled service
managers are simply ignored.
Would that work? Or is that exactly what you're planning to propose?
I don't think using just one USE flag would be as safe, unless this is only
an issue for daemontools. Tons of stuff tries to pull in systemd, but
blockers generally prevent you from making a mess that way.
-MD
>
[-- Attachment #2: Type: text/html, Size: 1912 bytes --]
next prev parent reply other threads:[~2024-09-27 0:09 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-23 20:14 [gentoo-user] Wayland! Beware of! Alan Mackenzie
2024-09-23 21:11 ` Eli Schwartz
2024-09-23 22:08 ` Alan Mackenzie
2024-09-23 22:54 ` Eli Schwartz
2024-09-24 11:30 ` [gentoo-user] --depclean and openrc [Was: Wayland! Beware of!] Alan Mackenzie
2024-09-24 11:40 ` Arsen Arsenović
2024-09-24 12:34 ` [gentoo-user] --depclean and openrc Alan Mackenzie
2024-09-24 15:24 ` Eli Schwartz
2024-09-24 18:15 ` Alan Mackenzie
2024-09-27 0:09 ` Mitchell Dorrell [this message]
2024-09-24 15:15 ` [gentoo-user] --depclean and openrc [Was: Wayland! Beware of!] Eli Schwartz
2024-09-24 18:53 ` Alan Mackenzie
2024-09-24 19:36 ` Eli Schwartz
2024-10-25 19:22 ` Alan Mackenzie
2024-10-26 3:10 ` Walter Dnes
2024-10-27 1:53 ` Eli Schwartz
2024-10-27 22:52 ` Alan Mackenzie
2024-10-27 23:14 ` Eli Schwartz
2024-09-25 0:32 ` Matt Jolly
2024-09-24 0:43 ` [gentoo-user] Wayland! Beware of! Michael Orlitzky
2024-09-24 0:52 ` Mitchell Dorrell
2024-09-24 1:13 ` Matt Jolly
2024-09-24 1:52 ` Eli Schwartz
2024-09-24 9:46 ` Mitchell Dorrell
2024-09-25 0:14 ` Matt Jolly
2024-09-24 10:05 ` Dr Rainer Woitok
2024-09-24 22:00 ` Walter Dnes
2024-09-25 1:42 ` Eli Schwartz
2024-09-25 10:00 ` Walter Dnes
2024-09-25 11:53 ` Arsen Arsenović
2024-09-25 22:21 ` Walter Dnes
2024-09-26 0:25 ` Eli Schwartz
2024-09-26 5:08 ` Walter Dnes
2024-09-26 19:18 ` James Cloos
2024-09-25 14:26 ` Eli Schwartz
2024-09-25 14:40 ` jay
2024-09-26 0:19 ` Michael Orlitzky
2024-09-23 21:12 ` Arsen Arsenović
2024-09-23 21:20 ` Wol
2024-09-23 22:53 ` karl
2024-09-24 7:10 ` Wols Lists
2024-09-24 18:32 ` What is what (Re: [gentoo-user] Wayland! Beware of!) karl
2024-09-24 23:44 ` Wols Lists
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=CAHqckJ2-88EX9eeVJZ53kM4dKLMGwmt5LPROXsV_vVxEZB42rw@mail.gmail.com \
--to=mwd@psc.edu \
--cc=gentoo-user@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