Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] sstate: Convert to use ':' as a filename sperator and use SSTATE_SWSPEC globally
Date: Fri, 20 Dec 2013 12:37:28 +0000	[thread overview]
Message-ID: <1387543048.6402.96.camel@ted> (raw)
In-Reply-To: <20131220123348.GV3706@jama>

On Fri, 2013-12-20 at 13:33 +0100, Martin Jansa wrote:
> On Fri, Dec 20, 2013 at 12:06:02PM +0000, Richard Purdie wrote:
> > Currently the code has problems differentiating between "gcc-cross" and "gcc-cross-initial"
> > sstate files. We could add in a ton of special casing but tests show this isn't scaling
> > well. Using a more unique separator resolves the issue.
> > 
> > The choice of which separator to use is a hard one. We need something which isn't commonly
> > used in PN, PV, PR, *_OS and *_ARCH which rules out '-', '_' and it needs to work ok with
> > webservers/http which makes ';' and '%' harder.
> > 
> > The change also sets SSTATE_SWSPEC globally since writing out differently named siginfo
> > files for the fetch/unpack/patch tasks is a waste of diskspace, the hashes match for
> > all PN in the majority of cases and if they don't, its not a big issue as the hash is
> > different. This makes the results from sstate debugging more understandable.
> 
> Can you mention why :: is sometimes used in SWSPEC?
> 
> I guess it's again just for easier differentianting, but maybe it should
> be mentioned in commit message.

Its so there are the same number of fields in there, its just empty for
the non-arch specific cases. 

Cheers,

Richard




      reply	other threads:[~2013-12-20 12:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-20 12:06 [PATCH] sstate: Convert to use ':' as a filename sperator and use SSTATE_SWSPEC globally Richard Purdie
2013-12-20 12:33 ` Martin Jansa
2013-12-20 12:37   ` Richard Purdie [this message]

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=1387543048.6402.96.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=martin.jansa@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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