public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Andrew Nowa Ammerlaan <andrewammerlaan@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] 2024-02-26-debianutils-drops-installkernel-dep: add news item v2
Date: Wed, 28 Feb 2024 13:34:48 +0100	[thread overview]
Message-ID: <e816fd01-d8bf-40a2-9eb0-5f9aaaac1ff9@gentoo.org> (raw)
In-Reply-To: <20240227101254.2b26dd6b-e241-4505-a335-2cdd82ed797e@korelogic.com>

On 27/02/2024 18:24, Hank Leininger wrote:
> On 2024-02-27, andrewammerlaan wrote:
> 
>> Until recently, sys-apps/debianutils was in turn pulled in by
>> app-misc/ca-certificates, an essential package installed on many
>> systems. This is no longer the case.[2]. As a result many users may find
>> that sys-apps/debianutils and therefore sys-kernel/installkernel are no
>> longer part of the dependency graph and will therefore be cleaned up by
>> "emerge --depclean".
> 
> Sorry for speaking up late: I (mis)read the second sentence differently
> from others in this thread, apparently.
> 
> "This is no longer the case." might apply to the first part of the
> previous sentence, "was in turn pulled in by".
> 
> Or it might apply to the second part, "an essential package installed on
> many systems."
> 
> I think what's meant is the former, it is no longer pulled in. But
> someone reading this cold could be forgiven for reading that as
> "ca-certificates is no longer an essential package".
> 
> Unfortunately my recommendation would be to restore the mention of a
> dependency, in some form or fashion, which seems to be something that
> was removed due to earlier feedback in this thread.
> 
> Maybe:
> 
> Until recently, sys-apps/debianutils was in turn pulled in by
> app-misc/ca-certificates, an essential package installed on many
> systems. That package no longer depends on sys-apps/debianutils.  As a
> result many users may find that sys-apps/debianutils and therefore
> sys-kernel/installkernel are no longer part of the dependency graph and
> will therefore be cleaned up by "emerge --depclean".

I rewrote this paragraph like this:

Until recently, sys-apps/debianutils was in turn pulled in by
app-misc/ca-certificates, an essential package installed on many
systems. However, this dependency of app-misc/ca-certificates on
sys-apps/debianutils was removed[2]. As a result many users may find
that sys-apps/debianutils and therefore sys-kernel/installkernel are no
longer part of the dependency graph and will therefore be cleaned up by
"emerge --depclean".

I think this way it should be very clear what has changed to cause the 
problem.

Best regards,
Andrew


      reply	other threads:[~2024-02-28 12:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-26 17:13 [gentoo-dev] 2024-02-26-debianutils-drops-installkernel-dep: add news item Andrew Nowa Ammerlaan
2024-02-26 22:39 ` Lucio Sauer
2024-02-27  2:28   ` Oskari Pirhonen
2024-02-27  4:23     ` Andrew Nowa Ammerlaan
2024-02-27  3:55 ` [gentoo-dev] " Duncan
2024-02-27  4:21   ` Eli Schwartz
2024-02-27  4:58   ` Andrew Nowa Ammerlaan
2024-02-27  6:26 ` [gentoo-dev] " Ulrich Mueller
2024-02-27  6:44   ` [gentoo-dev] 2024-02-26-debianutils-drops-installkernel-dep: add news item v2 Andrew Nowa Ammerlaan
2024-02-27 17:24     ` Hank Leininger
2024-02-28 12:34       ` Andrew Nowa Ammerlaan [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e816fd01-d8bf-40a2-9eb0-5f9aaaac1ff9@gentoo.org \
    --to=andrewammerlaan@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