All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Cc: Frans Meulenbroeks <fransmeulenbroeks@gmail.com>,
	Denys Dmytriyenko <denis@denix.org>
Subject: Re: [PATCH 0/1] Import own-mirrors class from OE
Date: Sun, 13 Mar 2011 09:56:58 -0600	[thread overview]
Message-ID: <4D7CE94A.5080706@mlbassoc.com> (raw)
In-Reply-To: <cover.1299940883.git.raj.khem@gmail.com>

On 03/12/2011 08:04 AM, Khem Raj wrote:
> Hi Richard
>
>
>
> Pull URL: git://git.openembedded.org/openembedded-core-contrib.git
>    Branch: kraj/own-mirror
>    Browse: http://git.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=kraj/own-mirror
>
> Thanks,
>      Khem Raj<raj.khem@gmail.com>
> ---
>
>
> Khem Raj (1):
>    own-mirrors.bbclass: Bring own-mirrors.bbclass from oe commit
>      0ef914b250df46a41348479446214575668943fb
>
>   meta/classes/own-mirrors.bbclass |   12 ++++++++++++
>   1 files changed, 12 insertions(+), 0 deletions(-)
>   create mode 100644 meta/classes/own-mirrors.bbclass
>

Poky/Yocto already has a mechanism for this by overriding PREMIRRORS
I would think sticking with one extension method would be better.

Here's what I have in my [Poky] DISTRO.conf:

SOURCE_DIR ?= "/opt/poky/sources"
PREMIRRORS = "\
http://.*/.*   file://${SOURCE_DIR}/ \n \
https://.*/.*  file://${SOURCE_DIR}/ \n \
ftp://.*/.*    file://${SOURCE_DIR}/ \n \
bzr://.*/.*    file://${SOURCE_DIR}/ \n \
cvs://.*/.*    file://${SOURCE_DIR}/ \n \
git://.*/.*    file://${SOURCE_DIR}/ \n \
hg://.*/.*     file://${SOURCE_DIR}/ \n \
osc://.*/.*    file://${SOURCE_DIR}/ \n \
p4://.*/.*     file://${SOURCE_DIR}/ \n \
svk://.*/.*    file://${SOURCE_DIR}/ \n \
svn://.*/.*    file://${SOURCE_DIR}/ \n"

Users can have their own mirror by defining SOURCE_DIR in local.conf

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



  parent reply	other threads:[~2011-03-13 16:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-12 15:04 [PATCH 0/1] Import own-mirrors class from OE Khem Raj
2011-03-12 15:04 ` [PATCH 1/1] own-mirrors.bbclass: Bring own-mirrors.bbclass from oe commit 0ef914b250df46a41348479446214575668943fb Khem Raj
2011-03-13 15:56 ` Gary Thomas [this message]
2011-03-13 16:13   ` [PATCH 0/1] Import own-mirrors class from OE Koen Kooi
2011-03-13 17:00     ` Gary Thomas
2011-03-13 18:50       ` Chris Larson
2011-03-13 22:18         ` Gary Thomas
2011-03-14  7:58           ` Koen Kooi
2011-03-15  1:11         ` Richard Purdie
2011-03-14 16:45   ` Tom Rini
2011-03-15  1:23 ` 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=4D7CE94A.5080706@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=denis@denix.org \
    --cc=fransmeulenbroeks@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 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.