All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: <poky@yoctoproject.org>
Subject: Re: How to create a PREMIRROR
Date: Fri, 9 Mar 2012 09:58:05 -0600	[thread overview]
Message-ID: <4F5A288D.9010900@windriver.com> (raw)
In-Reply-To: <9F69795E29C890408AC2DAF646C89BB379D1059697@MAILBOX.arc.local>

On 3/9/12 9:40 AM, Zoufal Andreas wrote:
> Hello everybody,
>
> I am new here in this mailing list. We are starting to use Yocto/Poky for an
> embedded project, and we have the need to collect all source code in our SVN
> repository for the case internet is not available. I think using PREMIRRORS (and
> SSTATE_MIRRORS for speedup) is the right way?
>
> How to create and maintain a local PREMIRRROR? What is the best practice? I’m
> pretty sure this is not the first time for this question, so can you give me
> some hints for a good documentation, or advices?

For the premirrors, what I've done is start a new build directory.. setup my 
DL_DIR to some place "safe".. and then do a "bitbake -c fetchall world"

I then export my DL_DIR for others via NFS, FTP, HTTPS, etc... whatever is 
appropriate within your organization -- then everyone else uses PREMIRROR 
settings to use that DL_DIR.

For the SSTATE_MIRROR, you can do something similar... but sstate_mirroring is 
really only useful if everyone is on a fast link.  In my experience anything 
slower then a gigabit link and it's usually (not always) faster to compile stuff 
locally, then pull from an sstate_mirror.

(Also if you have problems with an sstate_mirror, please let us know.  Not a lot 
of people are using them yet -- I had some issues w/ 1.1 and the sstate being 
used by multiple userids, but I believe these are resolved in newer versions.)

--Mark

> Thanx, Andi
>
> *ANDREAS ZOUFAL
> *Engineer
> Safety & Security Department
> Video and Security Technology
>
> **
>
> *AIT Austrian Institute of Technology GmbH
> *Donau-City-Straße 1 | 1220 Vienna | Austria
> T +43(0) 50550-4266 | F +43(0) 50550-4150
> _andreas.zoufal@ait.ac.at <mailto:andreas.zoufal@ait.ac.at>_|
> _http://www.ait.ac.at__
> _
> FN: 115980 i HG Wien | UID: ATU14703506
> This email and any attachments thereto, is intended only for use by the
> addressee(s) named herein and may contain legally privileged and/or confidential
> information. If you are not the intended recipient, please notify the sender by
> return e-mail or by telephone and delete this message from your system and any
> printout thereof. Any unauthorized use, reproduction, or dissemination of this
> message is strictly prohibited. Please note that e-mails are susceptible to
> change. AIT Austrian Institute of Technology GmbH shall not be liable for the
> improper or incomplete transmission of the information contained in this
> communication, nor shall it be liable for any delay in its receipt.
>
>
>
> _______________________________________________
> poky mailing list
> poky@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky



  reply	other threads:[~2012-03-09 15:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-09 15:40 How to create a PREMIRROR Zoufal Andreas
2012-03-09 15:58 ` Mark Hatle [this message]
2012-03-10 10:42   ` Zoufal Andreas
2012-03-12 15:26     ` Mark Hatle
2012-03-12 15:43       ` Gary Thomas
2012-03-12 15:50         ` Robert P. J. Day

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=4F5A288D.9010900@windriver.com \
    --to=mark.hatle@windriver.com \
    --cc=poky@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.