Patchwork local.conf.sample: add PATH to SSTATE_MIRRORS comments

login
register
mail settings
Submitter Paul Eggleton
Date Oct. 11, 2012, 1:27 p.m.
Message ID <1349962030-9309-1-git-send-email-paul.eggleton@linux.intel.com>
Download mbox | patch
Permalink /patch/38091/
State Accepted
Commit 40cf43c1c2fa15d0ee4bcc1226d9184747695b88
Headers show

Comments

Paul Eggleton - Oct. 11, 2012, 1:27 p.m.
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(-)
Saul Wold - Oct. 12, 2012, 6:07 p.m.
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!

Sau!
Paul Eggleton - Oct. 12, 2012, 6:20 p.m.
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
Marcin Juszkiewicz - Oct. 12, 2012, 6:22 p.m.
W dniu 12.10.2012 20:07, Saul Wold pisze:
> On 10/11/2012 06:27 AM, Paul Eggleton wrote:

>>   meta/conf/local.conf.sample |    7 +++++--
>>   1 file changed, 5 insertions(+), 2 deletions(-)

> I think this is really a Poky File, so should go to the
> poky@yoctoproject.org!

For me this file is part of OE-Core so list is proper. If OE-Core has
some Poky files then maybe consider moving them to separate layer?

Look at OE-Core from perspective of external developers. They change
files and then send patches here. Would you say them "go to other ML
with it" just because of history relations when they did proper thing?
Anders Darander - Oct. 15, 2012, 5:34 a.m.
* Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org> [121012 20:19]:

> W dniu 12.10.2012 20:07, Saul Wold pisze:
> > On 10/11/2012 06:27 AM, Paul Eggleton wrote:

> >>   meta/conf/local.conf.sample |    7 +++++--
> >>   1 file changed, 5 insertions(+), 2 deletions(-)

> > I think this is really a Poky File, so should go to the
> > poky@yoctoproject.org!

> For me this file is part of OE-Core so list is proper. If OE-Core has
> some Poky files then maybe consider moving them to separate layer?

For me, that's also correct.

If a file exists in oe-core, it's an oe-core file and patches goes here.

> Look at OE-Core from perspective of external developers. They change
> files and then send patches here. Would you say them "go to other ML
> with it" just because of history relations when they did proper thing?

> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Paul Eggleton - Oct. 15, 2012, 8:45 a.m.
On Monday 15 October 2012 07:34:15 Anders Darander wrote:
> * Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org> [121012 20:19]:
> > W dniu 12.10.2012 20:07, Saul Wold pisze:
> > > On 10/11/2012 06:27 AM, Paul Eggleton wrote:
> > >>   meta/conf/local.conf.sample |    7 +++++--
> > >>   1 file changed, 5 insertions(+), 2 deletions(-)
> > > 
> > > I think this is really a Poky File, so should go to the
> > > poky@yoctoproject.org!
> > 
> > For me this file is part of OE-Core so list is proper. If OE-Core has
> > some Poky files then maybe consider moving them to separate layer?
> 
> For me, that's also correct.
> 
> If a file exists in oe-core, it's an oe-core file and patches goes here.

I don't think anyone's actually disputing that. OE-Core patches always go to 
the OE-Core list, as happened in this case.

Cheers,
Paul

Patch

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