From: Saul Wold <sgw@linux.intel.com>
To: Chris Larson <clarson@kergoth.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] gtk-icon-cache: Fix rdepends construction
Date: Thu, 31 Jan 2013 12:19:30 -0800 [thread overview]
Message-ID: <510AD1D2.7060106@linux.intel.com> (raw)
In-Reply-To: <CABcZAN=Q=HYZ94QUahweLDHuiZDC7xd98F4nEbmMgZ5ze4tJhA@mail.gmail.com>
On 01/31/2013 11:50 AM, Chris Larson wrote:
>
> On Thu, Jan 31, 2013 at 12:50 PM, Chris Larson <clarson@kergoth.com
> <mailto:clarson@kergoth.com>> wrote:
>
> On Thu, Jan 31, 2013 at 12:11 PM, Saul Wold <sgw@linux.intel.com
> <mailto:sgw@linux.intel.com>> wrote:
>
> - rdepends = d.getVar('RDEPENDS_%s' % pkg, True)
> - rdepends = rdepends + ' ' + d.getVar('MLPREFIX') +
> "hicolor-icon-theme"
> - d.setVar('RDEPENDS_%s' % pkg, rdepends)
> + rdepends = ' ' + d.getVar('MLPREFIX') +
> "hicolor-icon-theme"
> + d.appendVar('RDEPENDS_%s' % pkg, rdepends)
>
>
> The new version isn't using a getVar of the old rdepends at all, so
> it's just replacing it every time. Is that really what you intended
> here? Wouldn't a getVar() or '' be a better approach? Further, the
> '' + d.getVar('MLPREFIX') is pointless if you aren't including the
> original value, as it adds a separator to the beginning when there's
> nothing to separate.
>
>
> Erm, ignore this, I'm apparently blind as a bat if I can't see
> 'appendVar' :)
No problem, I have had those days also.
Sau!
> --
> Christopher Larson
prev parent reply other threads:[~2013-01-31 20:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-31 19:11 [PATCH] gtk-icon-cache: Fix rdepends construction Saul Wold
2013-01-31 19:50 ` Chris Larson
2013-01-31 19:50 ` Chris Larson
2013-01-31 20:19 ` Saul Wold [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=510AD1D2.7060106@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=clarson@kergoth.com \
--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