All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: Richard Purdie <rpurdie@linux.intel.com>
Cc: poky@o-hand.com
Subject: Re: SVN woes persist
Date: Fri, 22 Oct 2010 08:04:01 -0600	[thread overview]
Message-ID: <4CC199D1.3000309@mlbassoc.com> (raw)
In-Reply-To: <1287755439.16386.736.camel@rex>

On 10/22/2010 07:50 AM, Richard Purdie wrote:
> On Thu, 2010-10-07 at 17:15 -0600, Gary Thomas wrote:
>> I updated to include these changes and gave it a try.  Here's what I did:
>>
>>     % mkdir /work/new_build
>>     % cd /work/poky_tree
>>     % . poky-init-build-env /work/new_build
>>       ... adjust DL_DIR, etc in conf/local.conf
>>           SSTATE_MIRRORS is not defined yet
>>     % bitbake some-image
>>
>>     % mv sstate-cache sstate
>>     % mv tmp tmp.old
>>       ... adjust conf/local.conf to set SSTATE_MIRRORS like this
>>           SSTATE_MIRRORS ?= "\
>>           file://.* file:///work/new_build/sstate/"
>>
>>     % bitbake some-image
>>
>> First of all, it took an incredible length of time (maybe a minute on my fast machine)
>> to even move past the resolve step.  Then it went off spewing lines about the state files
>> (sadly I didn't save them).  It then proceeded to run through some 322 steps, telling me
>> more about state files.  This took quite some time.  Then it seemed to just start the
>> normal build all over, apparently without regard to any of the sstate info.
>>
>> Did I miss something?  Is this how it should work?
>>
>> Sorry to be such a pain over this, but I'd really like to see this part working.
>> If there's something I can help with it, please let me know - I know my way around
>> Python code, but I don't know all the internals of how you expect this to work.
>
> Sorry not to get back to you sooner, I'm being pulled in a few different
> directions and we're coming up to release.
>
> In my own tests I've noticed a few issues and I've just pushed a number
> of fixes into the master branch which should help in various areas.
>
> With regard to your specific test and problem, it shouldn't rebuild
> everything. It turns out that I'd tested with http:// mirror urls and
> not file:// ones which needed and extra piece of code to handle them
> correctly.
>
> Have another try with master and see if things are better this time!

Will do.

Should this address the similar issue with GIT packages.  These seem
to be updating every time as well:
   git_github.com.wrpseudo.pseudo.git.tar.gz
   git_git.pokylinux.org.wr-kernel-tools.git.tar.gz
   git_git.pokylinux.org.prelink-cross.git.tar.gz

I'm still hoping for a way to have a static (no network needed) setup
soon.  I have to provide such in a training for some of my customers
in about a month :-)

Thanks

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


  reply	other threads:[~2010-10-22 14:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4CADD32A.9010908@mlbassoc.com>
     [not found] ` <1286462951.15840.6345.camel@rex>
     [not found]   ` <4CADE06F.6040308@mlbassoc.com>
     [not found]     ` <4CADFA77.3070305@mlbassoc.com>
     [not found]       ` <1286475616.15840.6565.camel@rex>
     [not found]         ` <4CAE54A1.1080803@mlbassoc.com>
2010-10-22 13:50           ` SVN woes persist Richard Purdie
2010-10-22 14:04             ` Gary Thomas [this message]
2010-10-22 14:29               ` Richard Purdie
2010-10-22 17:55                 ` Gary Thomas
2010-10-23  0:56                   ` Richard Purdie

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=4CC199D1.3000309@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=poky@o-hand.com \
    --cc=rpurdie@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 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.