On 2 July 2010 01:40, Koen Kooi <[email protected]> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 01-07-10 17:50, Enrico Scholz wrote: >> Koen Kooi <[email protected]> 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="" But since there really don't appear to be any in tree users of this, I didn't bother to include the recipe in my patch (i assumed it would be trivial for anyone to do with an overlay). Opkg-native has no reason whatsoever to require gpg or curl. In the future, I may change opkg to have gpg and curl support be disabled by default and require them to be explicitly enabled with --enable-foo. Gpg is disabled by most users anyway and curl doesn't offer much over simply using wget, so why not make it the default? -Graham _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
