Re: [OE-core] whatever happened to a proposal for "read-only" sstate?

2017-02-04 Thread Robert P. J. Day
On Fri, 3 Feb 2017, Richard Purdie wrote: > On Fri, 2017-02-03 at 06:45 -0500, Robert P. J. Day wrote: > >   for purposes of teaching, i wanted to check into the feasibility of > > having students take advantage of a single shared state cache, but > > still have the option of building whatever

Re: [OE-core] whatever happened to a proposal for "read-only" sstate?

2017-02-04 Thread Robert P. J. Day
On Fri, 3 Feb 2017, Richard Purdie wrote: > On Fri, 2017-02-03 at 06:45 -0500, Robert P. J. Day wrote: > >   for purposes of teaching, i wanted to check into the feasibility of > > having students take advantage of a single shared state cache, but > > still have the option of building whatever

Re: [OE-core] whatever happened to a proposal for "read-only" sstate?

2017-02-03 Thread Patrick Ohly
On Fri, 2017-02-03 at 16:24 -0500, Robert P. J. Day wrote: > On Fri, 3 Feb 2017, Patrick Ohly wrote: > > > On Fri, 2017-02-03 at 14:14 -0500, Robert P. J. Day wrote: > > > is there a command that will tell you how much shared state info a > > > given build would be able to take advantage of? >

Re: [OE-core] whatever happened to a proposal for "read-only" sstate?

2017-02-03 Thread Robert P. J. Day
On Fri, 3 Feb 2017, Patrick Ohly wrote: > On Fri, 2017-02-03 at 14:14 -0500, Robert P. J. Day wrote: > > is there a command that will tell you how much shared state info a > > given build would be able to take advantage of? > > INHERIT += "buildstats-summary" in local.conf will print that >

Re: [OE-core] whatever happened to a proposal for "read-only" sstate?

2017-02-03 Thread Patrick Ohly
On Fri, 2017-02-03 at 14:14 -0500, Robert P. J. Day wrote: > is there a command that will tell you how much shared state info a > given build would be able to take advantage of? INHERIT += "buildstats-summary" in local.conf will print that information after a build is done. -- Best Regards,

Re: [OE-core] whatever happened to a proposal for "read-only" sstate?

2017-02-03 Thread Robert P. J. Day
On Fri, 3 Feb 2017, Richard Purdie wrote: > On Fri, 2017-02-03 at 06:45 -0500, Robert P. J. Day wrote: > >   for purposes of teaching, i wanted to check into the feasibility of > > having students take advantage of a single shared state cache, but > > still have the option of building whatever

Re: [OE-core] whatever happened to a proposal for "read-only" sstate?

2017-02-03 Thread Robert P. J. Day
On Fri, 3 Feb 2017, Richard Purdie wrote: > On Fri, 2017-02-03 at 06:45 -0500, Robert P. J. Day wrote: > >   for purposes of teaching, i wanted to check into the feasibility of > > having students take advantage of a single shared state cache, but > > still have the option of building whatever

Re: [OE-core] whatever happened to a proposal for "read-only" sstate?

2017-02-03 Thread Richard Purdie
On Fri, 2017-02-03 at 06:45 -0500, Robert P. J. Day wrote: >   for purposes of teaching, i wanted to check into the feasibility of > having students take advantage of a single shared state cache, but > still have the option of building whatever source they needed in > their > own *personal* sstate

[OE-core] whatever happened to a proposal for "read-only" sstate?

2017-02-03 Thread Robert P. J. Day
for purposes of teaching, i wanted to check into the feasibility of having students take advantage of a single shared state cache, but still have the option of building whatever source they needed in their own *personal* sstate cache. i found this reference from 2014: