Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Saul Wold <sgw@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] local.conf.sample: add PATH to SSTATE_MIRRORS comments
Date: Fri, 12 Oct 2012 19:20:48 +0100	[thread overview]
Message-ID: <4822639.IxouvdiMRb@helios> (raw)
In-Reply-To: <50785C63.5060303@linux.intel.com>

On Friday 12 October 2012 11:07:31 Saul Wold wrote:
> On 10/11/2012 06:27 AM, Paul Eggleton wrote:
> > The shared state cache as pointed to by SSTATE_DIR by default now has
> > two-character subdirectories to prevent there being an issue with too
> > many files in the same directory; also, native sstate packages will go
> > into a subdirectory named using the distro ID string. If you copy the
> > newly structured sstate cache to a mirror location (either local or
> > remote) and then point to it in SSTATE_MIRRORS, you need to append
> > "PATH" to the end of the mirror URL so that the path used by bitbake
> > before the mirror substitution is appended to the path used to access
> > the mirror.
> > 
> > Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
> > ---
> > 
> >   meta/conf/local.conf.sample |    7 +++++--
> >   1 file changed, 5 insertions(+), 2 deletions(-)
> > 
> > diff --git a/meta/conf/local.conf.sample b/meta/conf/local.conf.sample
> > index 04d947f..d181e75 100644
> > --- a/meta/conf/local.conf.sample
> > +++ b/meta/conf/local.conf.sample
> > @@ -194,9 +194,12 @@ PATCHRESOLVE = "noop"
> > 
> >   # would contain the sstate-cache results from previous builds (possibly
> >   from other # machines). This variable works like fetcher
> >   MIRRORS/PREMIRRORS and points to the # cache locations to check for the
> >   shared objects.
> > 
> > +# NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to
> > add PATH +# at the end as shown in the examples below. This will be
> > substituted with the +# correct path within the directory structure.
> > 
> >   #SSTATE_MIRRORS ?= "\
> > 
> > -#file://.* http://someserver.tld/share/sstate/ \n \
> > -#file://.* file:///some/local/dir/sstate/"
> > +#file://.* http://someserver.tld/share/sstate/PATH \n \
> > +#file://.* file:///some/local/dir/sstate/PATH"
> > 
> >   # CONF_VERSION is increased each time build/conf/ changes incompatibly
> >   and is used to # track the version of this file when it was generated.
> >   This can safely be ignored if
>
> I think this is really a Poky File, so should go to the
> poky@yoctoproject.org!

There is a version of the file in both repositories, I sent a patch for each 
one.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



  reply	other threads:[~2012-10-12 18:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-11 13:27 [PATCH] local.conf.sample: add PATH to SSTATE_MIRRORS comments Paul Eggleton
2012-10-12 18:07 ` Saul Wold
2012-10-12 18:20   ` Paul Eggleton [this message]
2012-10-12 18:22   ` Marcin Juszkiewicz
2012-10-15  5:34     ` Anders Darander
2012-10-15  8:45       ` Paul Eggleton

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=4822639.IxouvdiMRb@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=sgw@linux.intel.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox