* curious about setting of PROVIDES in bitbake.conf
@ 2014-06-18 13:10 Robert P. J. Day
2014-06-18 15:50 ` Paul Eggleton
0 siblings, 1 reply; 3+ messages in thread
From: Robert P. J. Day @ 2014-06-18 13:10 UTC (permalink / raw)
To: BitBake developer list
from current bitbake.conf file:
PROVIDES = ""
PROVIDES_prepend = "${PN} "
is there a reason that PROVIDES is set to null, only to immediately
set it based on the following line? is there some subtle issue this is
meant to address?
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: curious about setting of PROVIDES in bitbake.conf
2014-06-18 13:10 curious about setting of PROVIDES in bitbake.conf Robert P. J. Day
@ 2014-06-18 15:50 ` Paul Eggleton
2014-06-18 22:35 ` Robert P. J. Day
0 siblings, 1 reply; 3+ messages in thread
From: Paul Eggleton @ 2014-06-18 15:50 UTC (permalink / raw)
Cc: bitbake-devel
On Wednesday 18 June 2014 09:10:00 Robert P. J. Day wrote:
> from current bitbake.conf file:
>
> PROVIDES = ""
> PROVIDES_prepend = "${PN} "
>
> is there a reason that PROVIDES is set to null, only to immediately
> set it based on the following line? is there some subtle issue this is
> meant to address?
I think the intention is to set the initial value to blank, and ensure that
${PN} is the first item in the list (since _prepend gets applied later). If you
just simply had PROVIDES = "${PN}" then it could be overridden somewhere else
such that ${PN} was not in PROVIDES at all, which would be counter-intuitive.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: curious about setting of PROVIDES in bitbake.conf
2014-06-18 15:50 ` Paul Eggleton
@ 2014-06-18 22:35 ` Robert P. J. Day
0 siblings, 0 replies; 3+ messages in thread
From: Robert P. J. Day @ 2014-06-18 22:35 UTC (permalink / raw)
To: Paul Eggleton; +Cc: bitbake-devel
On Wed, 18 Jun 2014, Paul Eggleton wrote:
> On Wednesday 18 June 2014 09:10:00 Robert P. J. Day wrote:
> > from current bitbake.conf file:
> >
> > PROVIDES = ""
> > PROVIDES_prepend = "${PN} "
> >
> > is there a reason that PROVIDES is set to null, only to immediately
> > set it based on the following line? is there some subtle issue this is
> > meant to address?
>
> I think the intention is to set the initial value to blank, and
> ensure that ${PN} is the first item in the list (since _prepend gets
> applied later). If you just simply had PROVIDES = "${PN}" then it
> could be overridden somewhere else such that ${PN} was not in
> PROVIDES at all, which would be counter-intuitive.
ah, of course, i should have thought of that. duh.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2014-06-18 22:38 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-06-18 13:10 curious about setting of PROVIDES in bitbake.conf Robert P. J. Day
2014-06-18 15:50 ` Paul Eggleton
2014-06-18 22:35 ` Robert P. J. Day
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.