From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH v2] opkg recipe overhaul - removal of opkg-nogpg and opkg-nogpg-nocurl.
Date: Tue, 13 Jul 2010 07:57:51 +0200 [thread overview]
Message-ID: <20100713055751.GE15231@jama> (raw)
In-Reply-To: <AANLkTimjZRbz8vPEG4xJzzjuebgHitB3NdbqyCywWNdg@mail.gmail.com>
On Tue, Jul 13, 2010 at 02:46:09PM +0930, Graham Gower wrote:
> Bump.
Seems OK for SHR (we don't really need curl or gpg).
> On 30 June 2010 14:24, Graham Gower <graham.gower@gmail.com> wrote:
> > None of the distros in OE appear to want/need gpg or curl support in opkg;
> > so have opkg.inc remove them by default. This diff makes things more consistent
> > across all distros/tasks/images.
> >
> > The slugos recipe is kept intact and further divided from the more modern
> > recipes. The opkg-native recipe is the sane-srcrev version even when building
> > slugos, which should allow for changes to opkg related bbclasses without
> > breaking the slugos build.
> >
> > Build tested for qemumipsel/minimal-image and nslu2/slugos-image.
> > minimal-image builds 10% quicker in my setup and is 1mb smaller.
> > ---
> >
> > v2:
> > A stray missing double quote makes the last patch a no go.
Regards,
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
next prev parent reply other threads:[~2010-07-13 6:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-30 4:26 [PATCH] opkg recipe overhaul - removal of opkg-nogpg and opkg-nogpg-nocurl Graham Gower
2010-06-30 4:54 ` [PATCH v2] " Graham Gower
2010-07-01 7:05 ` Khem Raj
2010-07-01 14:55 ` Enrico Scholz
2010-07-01 15:03 ` Koen Kooi
2010-07-01 15:50 ` Enrico Scholz
2010-07-01 16:10 ` Koen Kooi
2010-07-01 22:16 ` Graham Gower
2010-07-02 0:17 ` Graham Gower
2010-07-01 15:52 ` Tom Rini
2010-07-13 5:16 ` Graham Gower
2010-07-13 5:57 ` Martin Jansa [this message]
2010-07-15 7:32 ` Martin Jansa
2010-07-24 9:43 ` Khem Raj
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=20100713055751.GE15231@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-devel@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.