public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: coding style question about obsoleted packages
Date: Wed, 29 Apr 2020 05:28:21 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.21.2004290518370.6773@localhost.localdomain> (raw)


  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?

rday

p.s. YP reference maual, "migration to 3.1" section, does indeed
mention that console-tools is deleted, but neglects to mention its
replacement with kbd ... i've made a note of that and will add that
along with other changes to the ref manual at some point for clarity.

             reply	other threads:[~2020-04-29  9:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-29  9:28 Robert P. J. Day [this message]
2020-04-29 13:01 ` [OE-core] coding style question about obsoleted packages Richard Purdie

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=alpine.LFD.2.21.2004290518370.6773@localhost.localdomain \
    --to=rpjday@crashcourse.ca \
    --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