From: Gary Thomas <gary@mlbassoc.com>
To: Chris Larson <clarson@kergoth.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/1] Import own-mirrors class from OE
Date: Sun, 13 Mar 2011 16:18:09 -0600 [thread overview]
Message-ID: <4D7D42A1.80106@mlbassoc.com> (raw)
In-Reply-To: <AANLkTikQ-kF5u6AAKmWojmuP3xGZB4EPR0RkhhSsWAns@mail.gmail.com>
On 03/13/2011 12:50 PM, Chris Larson wrote:
> On Sun, Mar 13, 2011 at 10:00 AM, Gary Thomas<gary@mlbassoc.com> wrote:
>> Ask Richard? I was just pointing out that Poky/Yocto already has a
>> mechanism;
>> perhaps the OE one is better, who knows.
>
> There seems to be some confusion here. PREMIRRORS isn't a
> "poky/yocto" mechanism. It started in OE, and stills works just fine
> there (it's implemented in bitbake). own-mirrors is simply a
> convenience to make premirrors manipulation easier for the user. If
> convenience and usability isn't a priority for poky/yocto, I'd be
> curious to hear the reasoning.
Fair enough; I was merely commenting on how I had been told to handle this
in Poky/Yocto. If OE has a better way, perhaps it makes sense for it to
be available in both OE-CORE and Poky/Yocto.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2011-03-13 22:19 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
2011-03-13 18:50 ` Chris Larson
2011-03-13 22:18 ` Gary Thomas [this message]
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=4D7D42A1.80106@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=clarson@kergoth.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.