From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: OpenEmbedded Devel List
<openembedded-devel@lists.openembedded.org>,
Otavio Salvador <otavio@ossystems.com.br>,
openembedded-core@lists.openembedded.org
Subject: Re: [oe] any value in keeping the backward compat "task-core" stuff?
Date: Mon, 14 Jul 2014 06:31:18 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.11.1407140627370.6362@localhost> (raw)
In-Reply-To: <3833732.EFEfTvAqk5@peggleto-mobl5.ger.corp.intel.com>
On Mon, 14 Jul 2014, Paul Eggleton wrote:
> On Friday 11 July 2014 20:39:04 Otavio Salvador wrote:
> > On Thu, Jul 10, 2014 at 12:21 PM, Robert P. J. Day
> >
> > <rpjday@crashcourse.ca> wrote:
> > > a number of the current packagegroup recipe files still have
> > >
> > > backward compatibility support for the old "task-core" names, seems
> > > like that's been there for well over a year, would it be safe to
> > > finally just toss that? seems like everyone's had enough time to make
> > > the move to the new names, and it would be clearer to not confuse the
> > > proper use of the word "task" these days.
> >
> > I agree; however this question should also be send to oe-core mailing
> > list (added in Cc)
>
> I agree as well; these should go. I know there are some who want to
> keep these indefinitely for upgrade purposes, but I think there's a
> limit to how long they should stay around in OE-Core. They can
> always be preserved in bbappends for those that do want to keep
> them.
getting rid of all that "task-core" stuff in packagegroups looks
pretty easy, except for this snippet in
packagegroup-core-full-cmdline.bb:
packages = d.getVar("PACKAGES", True).split()
for pkg in packages:
if pkg.endswith('-dev'):
mapped = namemap.get(pkg[:-4], None)
if mapped:
mapped += '-dev'
elif pkg.endswith('-dbg'):
mapped = namemap.get(pkg[:-4], None)
if mapped:
mapped += '-dbg'
else:
mapped = namemap.get(pkg, None)
if mapped:
oldtaskname = mapped.replace("packagegroup-core", "task-core")
mapstr = " %s %s" % (mapped, oldtaskname)
d.appendVar("RPROVIDES_%s" % pkg, mapstr)
d.appendVar("RREPLACES_%s" % pkg, mapstr)
d.appendVar("RCONFLICTS_%s" % pkg, mapstr)
}
would one simply delete that last "if mapped:" conditional in its
entirety? or what?
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
next prev parent reply other threads:[~2014-07-14 10:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.LFD.2.11.1407101115390.10701@localhost>
2014-07-11 23:39 ` [oe] any value in keeping the backward compat "task-core" stuff? Otavio Salvador
2014-07-14 9:37 ` Paul Eggleton
2014-07-14 10:13 ` Robert P. J. Day
2014-07-14 10:31 ` Robert P. J. Day [this message]
2014-07-14 11:05 ` Paul Eggleton
2014-07-14 11:39 ` Robert P. J. Day
2014-07-14 12:14 ` Paul Eggleton
2014-07-14 12:22 ` Robert P. J. Day
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.11.1407140627370.6362@localhost \
--to=rpjday@crashcourse.ca \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
--cc=paul.eggleton@linux.intel.com \
/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