From: Gary Thomas <gary@mlbassoc.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Koen Kooi <koen@dominion.thruhere.net>
Subject: Re: [PATCH 0/1] Import own-mirrors class from OE
Date: Sun, 13 Mar 2011 11:00:23 -0600 [thread overview]
Message-ID: <4D7CF827.60904@mlbassoc.com> (raw)
In-Reply-To: <CCDB3981-855D-444D-A271-A863C2765CC4@dominion.thruhere.net>
On 03/13/2011 10:13 AM, Koen Kooi wrote:
>
> Op 13 mrt 2011, om 16:56 heeft Gary Thomas het volgende geschreven:
>
>> 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
>
> How is that easier and more maintainable than:
>
> INHERIT += "own-mirrors"
> SOURCE_MIRROR_URL = "/some/dir"
>
> ?
>
> Especially when more uri methods get added to the fetcher and oe-core.
Ask Richard? I was just pointing out that Poky/Yocto already has a mechanism;
perhaps the OE one is better, who knows.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2011-03-13 17:10 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 ` [PATCH 0/1] Import own-mirrors class from OE Gary Thomas
2011-03-13 16:13 ` Koen Kooi
2011-03-13 17:00 ` Gary Thomas [this message]
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=4D7CF827.60904@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=koen@dominion.thruhere.net \
--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