public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: "Arsen Arsenović" <arsen@gentoo.org>
Cc: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] --depclean and openrc
Date: Tue, 24 Sep 2024 12:34:25 +0000	[thread overview]
Message-ID: <ZvKx0TVYKFf7MX8P@MAC.fritz.box> (raw)
In-Reply-To: <8634lp1dpy.fsf@gentoo.org>

Hello, Arsen.

On Tue, Sep 24, 2024 at 13:40:57 +0200, Arsen Arsenović wrote:
> Alan Mackenzie <acm@muc.de> writes:

[ .... ]

> >> So, @system requires you to have any one of:

> >> - openrc
> >> - openrc-navi (a testing fork with openrc user services)
> >> - s6
> >> - systemd
> >> - runit
> >> - daemontools

> >> It's possible you have installed another one of these packages too. If
> >> you do, then virtual/service-manager will still be satisfied, and it
> >> will allow you to depclean openrc.

> > Yes, I have daemontools, needed as a component of a qmail variant.

> In that case, it'd be wise to 'emerge -n openrc' to prevent such
> trouble.

Yes.

> 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.

Thanks!

[ .... ]

> > The context of this discussion was an implication that the Gentoo
> > maintainers wouldn't make a change "that made everyone's systems
> > suddenly break".  I submitted a bug report about --depclean back in
> > the summer of 2021 (though I can't find that bug any more).  I think
> > it was closed as not-a-bug.

> Whoever closed it was wrong, frankly.

I've found the bug.  It was 803878.  The developer who responded treated
my bug as though it were a request for personal support, and he
completely evaded my point that it was a bug in portage which should be
fixed.  It was actually closed as TEST-REQUEST, whatever that means.  The
bug was never addressed.

> > There are several ways this could have been fixed, for example with
> > --depclean preserving packages in system, as well as world.

> That probably would not fix anything here, openrc is not in @system,
> virtual/service-manager is.

--depclean could preserve anything under a virtual in @system.

> > But it was regarded as not a bug.

> > So I think it is fair to say that the Gentoo developers are content for
> > some systems (in particular, mine) suddenly to break.

> Developers differ a good bit.. we generally try not to break things.

:-)

> > I am thus somewhat sceptical about things in Gentoo which may be based
> > on assumptions which don't hold in my system.  The new +wayland USE
> > flag kind of looked a bit like that to me.  Actually, it wasn't, so I
> > apologise for my opening post.
> -- 
> Arsen Arsenović

-- 
Alan Mackenzie (Nuremberg, Germany).


  reply	other threads:[~2024-09-24 12:34 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           ` Alan Mackenzie [this message]
2024-09-24 15:24             ` [gentoo-user] --depclean and openrc Eli Schwartz
2024-09-24 18:15               ` Alan Mackenzie
2024-09-27  0:09           ` [gentoo-user] --depclean and openrc [Was: Wayland! Beware of!] Mitchell Dorrell
2024-09-24 15:15         ` 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=ZvKx0TVYKFf7MX8P@MAC.fritz.box \
    --to=acm@muc.de \
    --cc=arsen@gentoo.org \
    --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