|
Re: Package postinstall dependencies - Introduction of PACKAGE_WRITE_DEPS
or PS_DEPENDS with the manual defining PS
and users thinking that it means any of:
Package Script / Populate Sysroot / Post Script
Also, all of Jussi's package changes are of the form:
or PS_DEPENDS with the manual defining PS
and users thinking that it means any of:
Package Script / Populate Sysroot / Post Script
Also, all of Jussi's package changes are of the form:
|
By
Randy MacLeod
·
#389
·
|
|
Re: Package postinstall dependencies - Introduction of PACKAGE_WRITE_DEPS
<jussi.kukkonen@...> wrote:
What about DEPENDS_PKG_SCRIPTS ?
--
Otavio Salvador O.S. Systems
http://www.ossystems.com.br http://code.ossystems.com.br
Mobile:
<jussi.kukkonen@...> wrote:
What about DEPENDS_PKG_SCRIPTS ?
--
Otavio Salvador O.S. Systems
http://www.ossystems.com.br http://code.ossystems.com.br
Mobile:
|
By
Otavio Salvador
·
#388
·
|
|
Re: Package postinstall dependencies - Introduction of PACKAGE_WRITE_DEPS
Richard asked me to test this and look at the remaining unhandled postinstalls. I've now done that, patches for the missing PACKAGE_WRITE_DEPS are in the "jku/wip-rss" branch in poky-contrib
Richard asked me to test this and look at the remaining unhandled postinstalls. I've now done that, patches for the missing PACKAGE_WRITE_DEPS are in the "jku/wip-rss" branch in poky-contrib
|
By
Jussi Kukkonen <jussi.kukkonen@...>
·
#387
·
|
|
Re: Package postinstall dependencies - Introduction of PACKAGE_WRITE_DEPS
Yes, there is. do_some_task[depends] += "some-recipe:some_other_task".
DEPENDS is just a neat way of setting [depends] on do_configure to the list of recipes in DEPENDS's do_populate_sysroot
Yes, there is. do_some_task[depends] += "some-recipe:some_other_task".
DEPENDS is just a neat way of setting [depends] on do_configure to the list of recipes in DEPENDS's do_populate_sysroot
|
By
Burton, Ross <ross.burton@...>
·
#386
·
|
|
Recipe Specific Sysroots - An Update
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=rpurdie/wip-rss
I've been quiet on this for a while but the patches are progressing and
I've been keeping this branch updated. Its proving a
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=rpurdie/wip-rss
I've been quiet on this for a while but the patches are progressing and
I've been keeping this branch updated. Its proving a
|
By
Richard Purdie
·
#385
·
|
|
Re: Package postinstall dependencies - Introduction of PACKAGE_WRITE_DEPS
...
Is there not already a mechanism for generically saying "I need <this> task of
<that> recipe to be completed before my <such-and-such> task can run" of which
DEPENDS and RDEPENDS are simply
...
Is there not already a mechanism for generically saying "I need <this> task of
<that> recipe to be completed before my <such-and-such> task can run" of which
DEPENDS and RDEPENDS are simply
|
By
Trevor Woerner
·
#384
·
|
|
Re: [OE-core] Patchwork and incoming patch testing
Is the testing process for OE patches formalized?
I'm not referring to the Yocto Project's release testing.
Is the testing process for OE patches formalized?
I'm not referring to the Yocto Project's release testing.
|
By
Trevor Woerner
·
#383
·
|
|
Re: Package postinstall dependencies - Introduction of PACKAGE_WRITE_DEPS
The sysroot requirements are actually quite varied. It really helps to
think about this from a task perspective which is how bitbake really
works.
In order to run do_fetch, there could be tools like
The sysroot requirements are actually quite varied. It really helps to
think about this from a task perspective which is how bitbake really
works.
In order to run do_fetch, there could be tools like
|
By
Richard Purdie
·
#382
·
|
|
Re: Layer index enhancements
I was wrong about this - the collection name is collected and used in the
dependency resolution. New layers / branches should have this information
populated, however we haven't collected collection
I was wrong about this - the collection name is collected and used in the
dependency resolution. New layers / branches should have this information
populated, however we haven't collected collection
|
By
Paul Eggleton <paul.eggleton@...>
·
#381
·
|
|
Re: Package postinstall dependencies - Introduction of PACKAGE_WRITE_DEPS
yes, I was missing the native piece in my thinking.... I see why this is
potentially a big problem for the sstate-cache.
The one thing I keep coming back to on DEPENDS (vs a more specific DEPENDS).
yes, I was missing the native piece in my thinking.... I see why this is
potentially a big problem for the sstate-cache.
The one thing I keep coming back to on DEPENDS (vs a more specific DEPENDS).
|
By
Mark Hatle <mark.hatle@...>
·
#380
·
|
|
Re: Package postinstall dependencies - Introduction of PACKAGE_WRITE_DEPS
I keep going around in circles on this. The naming would then match one
use of it rather than where the dependency is added. It makes less
sense when you think this could apply to preinsts and its
I keep going around in circles on this. The naming would then match one
use of it rather than where the dependency is added. It makes less
sense when you think this could apply to preinsts and its
|
By
Richard Purdie
·
#379
·
|
|
Re: Package postinstall dependencies - Introduction of PACKAGE_WRITE_DEPS
You're thinking too specifically about my example. What about ca-
certificates which needs ca-certificates-native to run its postinstall
at do_rootfs time?
Keep in mind a -native dependency doesn't
You're thinking too specifically about my example. What about ca-
certificates which needs ca-certificates-native to run its postinstall
at do_rootfs time?
Keep in mind a -native dependency doesn't
|
By
Richard Purdie
·
#378
·
|
|
Re: Package postinstall dependencies - Introduction of PACKAGE_WRITE_DEPS
I have seen other systems declare these in different ways. Things like:
RPROVIDES_pn += "user(name)"
RREQUIRES_pn += "user(name)"
Automation can declare provides and dependencies users that are
I have seen other systems declare these in different ways. Things like:
RPROVIDES_pn += "user(name)"
RREQUIRES_pn += "user(name)"
Automation can declare provides and dependencies users that are
|
By
Mark Hatle <mark.hatle@...>
·
#377
·
|
|
Package postinstall dependencies - Introduction of PACKAGE_WRITE_DEPS
One problem we're seeing with recipe specific sysroots (rss) is that
the dependencies package postinstalls have is badly represented.
For example, dbus adds a user and this needs tools from
One problem we're seeing with recipe specific sysroots (rss) is that
the dependencies package postinstalls have is badly represented.
For example, dbus adds a user and this needs tools from
|
By
Richard Purdie
·
#376
·
|
|
Layer index enhancements
Hi all,
We've done some work recently on the OE layer index [1] and I thought it might
be useful to give a summary of what's been implemented:
* Upgraded to Django 1.8. This was a bunch of work
Hi all,
We've done some work recently on the OE layer index [1] and I thought it might
be useful to give a summary of what's been implemented:
* Upgraded to Django 1.8. This was a bunch of work
|
By
Paul Eggleton <paul.eggleton@...>
·
#375
·
|
|
Re: Patchwork and incoming patch testing
This looks great, thanks.
What's the plan for these status updates -- is the idea that you go to patchwork UI to see the state of a specific patch set?
Or maybe a reply to either patch sender or even
This looks great, thanks.
What's the plan for these status updates -- is the idea that you go to patchwork UI to see the state of a specific patch set?
Or maybe a reply to either patch sender or even
|
By
Jussi Kukkonen <jussi.kukkonen@...>
·
#374
·
|
|
Re: Patchwork and incoming patch testing
Paul,
That is some impressive work by the team! Thank you all for the hard work and
bringing the plan to fruition - I'm sure this framework will benefit our
entire Community and will improve and
Paul,
That is some impressive work by the team! Thank you all for the hard work and
bringing the plan to fruition - I'm sure this framework will benefit our
entire Community and will improve and
|
By
Denys Dmytriyenko
·
#373
·
|
|
Patchwork and incoming patch testing
Hi all,
As some of you are aware some of my colleagues and I have been working on
improving how incoming patches are handled - initially for OE-Core but we hope
to arrive at something that will be
Hi all,
As some of you are aware some of my colleagues and I have been working on
improving how incoming patches are handled - initially for OE-Core but we hope
to arrive at something that will be
|
By
Paul Eggleton <paul.eggleton@...>
·
#372
·
|
|
Re: [oe] [yocto] OpenEmbedded Developers Meeting in Portland before ELC
Definitely plural! A conference phone with a number of microphones dotted around the room seems to be a sensible idea.
Ross
Definitely plural! A conference phone with a number of microphones dotted around the room seems to be a sensible idea.
Ross
|
By
Burton, Ross <ross.burton@...>
·
#371
·
|
|
Re: [yocto] OpenEmbedded Developers Meeting in Portland before ELC
Paul,
It's a great point. I have volunteered Mentor's teleconference, but the onsite pickup is always a challenge. Once we've finalized the location, I'll focus on making sure that we have a high
Paul,
It's a great point. I have volunteered Mentor's teleconference, but the onsite pickup is always a challenge. Once we've finalized the location, I'll focus on making sure that we have a high
|
By
Hudson, Sean <Sean_Hudson@...>
·
#370
·
|