From: Tom Rini <tom_rini@mentor.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH v2] opkg recipe overhaul - removal of opkg-nogpg and opkg-nogpg-nocurl.
Date: Thu, 01 Jul 2010 08:52:22 -0700 [thread overview]
Message-ID: <4C2CB9B6.1010509@mentor.com> (raw)
In-Reply-To: <i0ian8$pt3$1@dough.gmane.org>
Koen Kooi wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 01-07-10 16:55, Enrico Scholz wrote:
>> Graham Gower <graham.gower@gmail.com> writes:
>>
>>> None of the distros in OE
>> At least the openmoko SHR distribution fetches ipkg from network and
>> requires curl support hence.
>
> That's not true, with curl disabled, it calls (busybox) wget.
>
>>> appear to want/need gpg or curl support in opkg; so have opkg.inc
>>> remove them by default.
>> I do not think that supporting only offline mode (due to removal of
>> curl support) is a good idea. Although the opportunistic signature
>> verification is not secure, it would be imo bad to remove gpg support
>> completely because updating embedded devices in a secure manner is
>> important.
>>
>> A better way might be to conditionalize your '--disable-*' options
>> resp. make them depend on some DISTRO_FEATURE.
>
> Introducing USE flags would be a step backwards, so NAK on that.
Increasing (or decreasing...) USE flags, now there's a topic for the TSC...
--
Tom Rini
Mentor Graphics Corporation
next prev parent reply other threads:[~2010-07-01 15:57 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 [this message]
2010-07-13 5:16 ` Graham Gower
2010-07-13 5:57 ` Martin Jansa
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=4C2CB9B6.1010509@mentor.com \
--to=tom_rini@mentor.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox