[oe] [PATCH v2] opkg recipe overhaul - removal of opkg-nogpg and opkg-nogpg-nocurl.

[Graham Gower]

On 2 July 2010 07:46, Graham Gower <graham.gower at gmail.com> wrote:
> On 2 July 2010 01:40, Koen Kooi <k.kooi at student.utwente.nl> wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> On 01-07-10 17:50, Enrico Scholz wrote:
>>> Koen Kooi <k.kooi at student.utwente.nl> writes:
>>>
>>>>> 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.
>
> I don't like the idea of USE flags either. Every time you see one you
> would have to grep -r your tree to find out its impact.
>
>>>
>>> how would you reenable gpg and curl for https support then?
>>
>> By keeping the existing recipes?
>
> Or, by extending the defautl opkg_svn.bb recipe I have left behind.
>
> e.g. an opkg-fullyloaded.bb containing
> include opkg_svn.bb
> EXTRA_CFLAGS=""

And here's a tested version
$ cat opkg-fullyloaded_svn.bb
require opkg_svn.bb
DEPENDS = "curl gpgme openssl"
EXTRA_OECONF = ""

Is this recipe desirable? Put your hand up if you plan to use it, not
because "its nice to have the option".

-Graham