All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: BitBake developer list <bitbake-devel@lists.openembedded.org>
Subject: Re: wanting clarification on overrides, _append, += and combinations of those
Date: Sun, 25 Nov 2012 21:39:33 +0000	[thread overview]
Message-ID: <1353879573.21863.33.camel@ted> (raw)
In-Reply-To: <alpine.DEB.2.02.1211240938390.1166@oneiric>

On Sat, 2012-11-24 at 09:42 -0500, Robert P. J. Day wrote:
> one more question, if i might ...
> 
> On Sat, 24 Nov 2012, Robert P. J. Day wrote:
> 
> > RDEPENDS_python-smartpm_append = " python-smartpm-backend-rpm python-codecs python-textutils python-xml"
> > RDEPENDS_python-smartpm_append += " python-fcntl python-pickle python-crypt python-compression python-shell"
> > RDEPENDS_python-smartpm_append += " python-resource python-netclient python-threading python-unixadmin"
> 
>   is there a reason the above couldn't have been written as something
> like:
> 
> RDEPENDS_python-smartpm += "python-fcntl python-pickle python-crypt python-compression python-shell"
> RDEPENDS_python-smartpm += "python-resource python-netclient python-threading python-unixadmin"
> 
>   as i understand it, the purpose of "_append" is to give the
> developer control over being able to append something at the very end
> of the processing -- in other words, it's used when ordering is
> important.
> 
>   but is there any ordering issue when simply creating the value of
> RDEPENDS?  does it matter how the items are ordered there?  if not,
> then using "_append" seems like overkill.

In this case I'd agree, it does seem a little over the top.

Cheers,

Richard





  reply	other threads:[~2012-11-26  9:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-24 14:23 wanting clarification on overrides, _append, += and combinations of those Robert P. J. Day
2012-11-24 14:42 ` Robert P. J. Day
2012-11-25 21:39   ` Richard Purdie [this message]
2012-11-25 21:38 ` Richard Purdie
2012-11-26 11:19 ` Paul Eggleton
2012-11-26 11:53   ` Robert P. J. Day
2012-11-26 12:35   ` 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=1353879573.21863.33.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=rpjday@crashcourse.ca \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.