From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Paul McGougan <PMcGougan@topcon.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Question / issue
Date: Tue, 13 May 2014 08:10:02 +0100 [thread overview]
Message-ID: <1399965002.31891.148.camel@ted> (raw)
In-Reply-To: <C7589FE7B0DE58488F2B9BF79840E9D90D66FB2D@ADL-EXCHMBX1.TOPCON.com>
On Mon, 2014-05-12 at 23:31 +0000, Paul McGougan wrote:
> > -----Original Message-----
> > From: David Nyström [mailto:david.c.nystrom@gmail.com]
>
> > To me, Thats sound like a bug in the dependency parser.
> > It should not parse for changes in comments, i.e. in this case do_install_append
> > comments.
> >
> > Or perhaps in variable expansion, which could be avoided in commented
> > sections.
>
> Yes, I agree that the dependency parser should be altered.
>
> I would suggest your 2nd suggestion would be the most appropriate, i.e. do not perform variable expansion in commented lines.
Its easy to think that at a first glance.
What if the variable being expanded expands to something multiline and
some of those lines are not comments though?
Bitbake's behaviour has always been to expand variables first, then
follow with other things like execution. The dependency parsing follows
the behaviour and includes them as dependencies because of the above
multiline issue.
So rightly or wrongly, the code does at least behave consistently at the
moment and its not as easy to change as you'd first think.
I make no claims about whether multiline expansion is a good thing, just
that these issues are there and that they're hard to change as the
impact isn't always as you'd expect. The behaviour has been like this
for a long time too.
Cheers,
Richard
next prev parent reply other threads:[~2014-05-13 7:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-09 5:14 Question / issue Paul McGougan
2014-05-09 14:44 ` Bruce Ashfield
2014-05-12 5:56 ` Paul McGougan
2014-05-12 11:03 ` Bruce Ashfield
2014-05-12 11:10 ` Paul Eggleton
2014-05-12 23:29 ` Paul McGougan
2014-05-12 18:43 ` David Nyström
2014-05-12 23:31 ` Paul McGougan
2014-05-13 7:10 ` Richard Purdie [this message]
2014-05-19 13:41 ` Stefano Babic
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=1399965002.31891.148.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=PMcGougan@topcon.com \
--cc=yocto@yoctoproject.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.