All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Berger <gmane@reliableembeddedsystems.com>
To: yocto@yoctoproject.org
Subject: Re: multi-user shared state
Date: Thu, 11 Jun 2015 17:28:09 +0300	[thread overview]
Message-ID: <55799AF9.1060607@reliableembeddedsystems.com> (raw)
In-Reply-To: <DB59870584238C45879465F0A2E5C3F17B01E6@IRVEXCHMB14.corp.ad.broadcom.com>

Hi,

On 06/10/2015 10:25 PM, Luke (Lucas) Starrett wrote:
> Hi,
> 
>  
> 
> I’m trying to understand the feasibility of shared-state across multiple
> users in a development environment.  Does anyone have first-hand
> experience with this?  Am I asking for trouble?

Have a look here [1] 3.2.1.2. Core System Development, and [2]

I did have troubles in the past. When I built e.g. for 2 different
boards both using the same compiler and the same sstate funny things
happened when 2 machines tried to work on the same package at the same
time. But everything should be fine as long as things work sequentially.
Don't know if the sstate mechanism works concurrently in the meantime.

> 
>  
> 
> If this is expected to work, a secondary question would be whether or
> not shared-state on a NFS mounted path works.  Any thoughts?

shared state works (and as a matter of fact everything on an nfs share
would work)

> 
>  
> 
> Thanks,
> 
>  
> 
> Luke Starrett     
> 
>  

[1] http://www.yoctoproject.org/docs/1.8/dev-manual/dev-manual.html
[2]
http://www.yoctoproject.org/docs/1.8/ref-manual/ref-manual.html#shared-state-cache
> 
> 
> 
> -- 
> 

Regards,

Robert

..."Teaching of beginners should be done by a master, not by a hack." -
Deming

My public pgp key is available,at:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x90320BF1




      parent reply	other threads:[~2015-06-11 14:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-10 19:25 multi-user shared state Luke (Lucas) Starrett
2015-06-10 19:56 ` Aníbal Limón
2015-06-11 14:28 ` Robert Berger [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=55799AF9.1060607@reliableembeddedsystems.com \
    --to=gmane@reliableembeddedsystems.com \
    --cc=yocto@yoctoproject.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 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.