From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] coding style question about obsoleted packages
Date: Wed, 29 Apr 2020 14:01:07 +0100 [thread overview]
Message-ID: <73d18db72183f0654ff8f8849590f1539b641cf6.camel@linuxfoundation.org> (raw)
In-Reply-To: <alpine.LFD.2.21.2004290518370.6773@localhost.localdomain>
On Wed, 2020-04-29 at 05:28 -0400, Robert P. J. Day wrote:
> just noticed that, in master branch, kbd recipe quite reasonably
> distinguishes itself from the much, much older console-tools package
> thusly:
>
> RREPLACES_${PN} = "console-tools"
> RPROVIDES_${PN} = "console-tools"
> RCONFLICTS_${PN} = "console-tools"
>
> all perfectly reasonable as long as console-tools actually existed as
> a recipe, but it was deleted some months ago:
>
> commit 320319f24dd1be300bc89c52b97d1703eab83029
> Author: Alexander Kanavin <alex.kanavin@gmail.com>
> Date: Wed Nov 20 14:44:51 2019 +0100
>
> console-tools: remove the recipe
>
> The last release of this was in 2002(!), kbd is the modern,
> supported alternative.
>
> and as best i can tell, there are no references to console-tools in
> the numerous layers i have checked out. under the circumstances,
> then,
> while it doesn't hurt to have that info above in the kbd recipe, is
> there any value?
>
> more generally, when a recipe is truly removed and obsoleted,
> should
> it be part of the removal process to get rid of such references to it
> to avoid slowly-accumulating cruft in the code base?
It in theory has implications for anyone doing on device upgrades so is
needed for that. We need to let this sit for at least a release or two
so people can transition, then it can be removed.
Cheers,
Richard
prev parent reply other threads:[~2020-04-29 13:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-29 9:28 coding style question about obsoleted packages Robert P. J. Day
2020-04-29 13:01 ` Richard Purdie [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=73d18db72183f0654ff8f8849590f1539b641cf6.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.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