From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: openembedded-devel@lists.openembedded.org
Subject: Re: missing trailing spaces in some "_prepend" expressions in oe-core
Date: Fri, 9 Jan 2015 07:57:54 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.11.1501090756330.10695@localhost> (raw)
In-Reply-To: <20150105162556.GL2484@jama>
On Mon, 5 Jan 2015, Martin Jansa wrote:
> On Mon, Jan 05, 2015 at 09:58:01AM -0500, Robert P. J. Day wrote:
> >
> > after running across a variable "_prepend" assignment that had no
> > trailing space, i did a quick grep through oe-core and ran across the
> > following, which would all seem to need that trailing space:
> >
> > $ grep -rn "DEPENDS_prepend.*[^ ]\"$" *
> > meta/classes/qt4e.bbclass:2:DEPENDS_prepend = "${QT4EDEPENDS}"
> > meta/classes/cpan_build.bbclass:27:DEPENDS_prepend = "${@cpan_build_dep_prepend(d)}"
> > meta/classes/autotools.bbclass:24:DEPENDS_prepend = "${@autotools_dep_prepend(d)}"
> > meta/classes/qt4x11.bbclass:2:DEPENDS_prepend = "${QT4DEPENDS}"
> > $
>
> e.g. QT4EDEPENDS QT4DEPENDS both end with space, so it's not causing
> any problem, but having the trailing space together with prepend is
> good.
>
> Only exception I can think of is when you really don't want to
> introduce extra space when the variable used in prepend/append is
> set to empty, but that's not an issue for DEPENDS (but important
> e.x. for tune .inc files)
>
> > and
> >
> > $ grep -rn "SRC_URI_prepend.*[^ ]\"$" *
> > meta/recipes-devtools/qemu/qemu_git.bb:10:SRC_URI_prepend = "git://git.qemu.org/qemu.git"
> > meta/recipes-devtools/qemu/qemu_2.2.0.bb:10:SRC_URI_prepend = "http://wiki.qemu-project.org/download/${BP}.tar.bz2"
> > $
> >
> > there may be more, i just left it at that, not sure if there's
> > something magic about those examples or whether they really should
> > have the space added, so i'll leave it with someone else to tweak.
not sure if i replied to this already, but if someone wants to tweak
those, i'll leave it up to them. obviously, as martin suggests,
they're not actually causing problems, but i'm just a style guide kind
of guy.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
prev parent reply other threads:[~2015-01-09 12:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-05 14:58 missing trailing spaces in some "_prepend" expressions in oe-core Robert P. J. Day
2015-01-05 16:25 ` Martin Jansa
2015-01-09 12:57 ` Robert P. J. Day [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=alpine.LFD.2.11.1501090756330.10695@localhost \
--to=rpjday@crashcourse.ca \
--cc=openembedded-devel@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 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.