From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>,
OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: whatever happened to a proposal for "read-only" sstate?
Date: Fri, 03 Feb 2017 14:18:12 +0000 [thread overview]
Message-ID: <1486131492.14144.70.camel@linuxfoundation.org> (raw)
In-Reply-To: <alpine.LFD.2.20.1702030641310.2549@localhost.localdomain>
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 cache.
>
> i found this reference from 2014:
>
> http://lists.openembedded.org/pipermail/openembedded-core/2014-August
> /096486.html
>
> but it seems clear nothing became of it; there's certainly no
> .bbclass
> file that matches that.
>
> what are the options for setting up something like this? or is that
> already supported and i'm just not seeing it?
It was never merged as its not really necessary, you can do this with
existing functionality.
Just point SSTATE_MIRRORS at the common shared directory and SSTATE_DIR
at the directory you want to be the personal one.
Cheers,
Richard
next prev parent reply other threads:[~2017-02-03 14:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-03 11:45 whatever happened to a proposal for "read-only" sstate? Robert P. J. Day
2017-02-03 14:18 ` Richard Purdie [this message]
2017-02-03 14:44 ` Robert P. J. Day
2017-02-03 19:14 ` Robert P. J. Day
2017-02-03 21:20 ` Patrick Ohly
2017-02-03 21:24 ` Robert P. J. Day
2017-02-03 21:49 ` Patrick Ohly
2017-02-04 17:12 ` Robert P. J. Day
2017-02-04 17:18 ` Robert P. J. Day
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=1486131492.14144.70.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=rpjday@crashcourse.ca \
/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.