linux/poky.git/meta/conf/distro/include/default-distrovars.inc, branch uninative-1.7

default-distrovars: add acl to DISTRO_FEATURES

2017-01-31T14:43:00+00:00

ACLs are pretty useful in the modern world, with security systems such as SELinux and Smack that use them extensively. As the overhead is minimal, add ACL to DEFAULT_DISTRO_FEATURES so that support for them is enabled by default. The overhead for core-image-sato is that coreutils, libarchive, and opkg link against libacl. The size increase of those packages is minimal, and libacl is 35kb. [ YOCTO #8200 ] (From OE-Core rev: 0c4d6dec32615af10fdaa4f1685b8c4f2a167feb) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

default-distrovars.inc: remove libidn from LGPLv2_WHITELIST_GPL-3.0

2016-09-20T14:11:08+00:00

The libidn recipe is now buildable in distros which blacklist GPL-3.0 without needing to be explicitly whitelisted (since it provides at least one non GPLv3 package). (From OE-Core rev: 63d6d014a0a3da8bf5689b27d1155492e2fdb0f2) Signed-off-by: Jackie Huang Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

default-distrovars.inc: remove libassuan from LGPLv2_WHITELIST_GPL-3.0

2016-04-03T14:51:35+00:00

The libassuan recipe is now buildable in distros which blacklist GPL-3.0 without needing to be explicitly whitelisted (since it provides at least one non GPLv3 package). (From OE-Core rev: 259b0f163922ce12e24dd6670cf28d987b37b676) Signed-off-by: Andre McCurdy Signed-off-by: Richard Purdie

base.bbclass: drop obsolete HOSTTOOLS_WHITELIST_GPL-3.0

2016-04-01T06:14:30+00:00

base.bbclass sets 'check_license' to False (and therefore skips license checking completely) for native, nativesdk, etc recipes (ie anything which could potentially be classed as "host tools"), so supporting a dedicated whitelist of GPLv3 host tools is not necessary. (From OE-Core rev: 8fc8b60005e7641861324c8541fb45058e7aab8e) Signed-off-by: Andre McCurdy Signed-off-by: Richard Purdie

default-distrovars.inc: remove gnutls + libtasn1 from LGPLv2_WHITELIST_GPL-3.0

2016-03-31T08:15:04+00:00

With the modern license handling code, gnutls and libtasn1 are both buildable in distros which blacklist GPL-3.0 without needing to be explicitly whitelisted (since they both provide at least one non GPLv3 package). (From OE-Core rev: 0a42e49bdcbc2f1f63b9d3fda9d4bc0f87a8eb01) Signed-off-by: Andre McCurdy Signed-off-by: Richard Purdie

libc-package.bbclass: add LOCALE_UTF8_IS_DEFAULT

2016-01-30T11:36:57+00:00

python hard-codes the encoding of many locales; for instance, en_US is always assumed to be ISO-8859-1, regardless of the actual encoding of the en_US locale on the system. cf https://hg.python.org/cpython/file/7841e9b614eb/Lib/locale.py#l1049, getdefaultlocale(), etc. This code appears to date back to python 2.0. The source of this hard-coding is Xorg's locale.alias but is ultimately justified by glibc's SUPPORTED. This causes problems on OE, because any locale lacking an explicit encoding suffix (e.g. en_US) is UTF-8. It has been this way from the beginning (svn r1). That is not a bug, per se -- no specification prohibits this AFAIK. But it seems to be at odds with virtually every other glibc-based distribution in existence. To avoid needlessly aggravating hidden bugs that nobody else might hit, it makes sense to disable this behavior such that locales are named precisely as specified by SUPPORTED. I suppose that reasonable minds may disagree on whether or not the current behavior is prudent; at the very least, this is likely to break IMAGE_LINGUAS settings. So let's create a new distro variable LOCALE_UTF8_IS_DEFAULT to allow either behavior. Set it to 0 and all your locales get named exactly like they are in SUPPORTED. Leave it at 1 to preserve current OE locale naming conventions. (From OE-Core rev: fcde0c43f7b57ec6f8201226ad98e6e46708d288) Signed-off-by: Richard Tollerton Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

qt4: remove recipes and classes

2016-01-07T13:40:14+00:00

Qt4 is no longer supportd upstream, but it is still needed for LSB compliancy. Qt4 recipes have been moved to a separate meta-qt4 layer to be consistent with meta-qt3 and meta-qt5. (From OE-Core rev: cb89d2b25b4edb1241bc5426a69a6bc44df9be2c) Signed-off-by: Alexander Kanavin Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

default-distrovars: remove less from WHITELIST_GPL-3.0

2015-11-16T11:39:33+00:00

As oe-core commit 37c8c2c5f6937520eaf9f5d981f9315e36eba4bb and fa7bdf96b8eb8b5078db38249c5c60ec511c35c6 said, Mark Nudelman (author of less) has given permission to utilize a generic 2-clause BSD, so we remove it from WHITELIST_GPL-3.0 which caused a QA Warning while INCOMPATIBLE_LICENSE += "GPLv3 LGPLv3 GPLv3+ LGPLv3+" ... |NOTE: INCLUDING less as buildable despite INCOMPATIBLE_LICENSE because it has been whitelisted ... (From OE-Core rev: 712c4ccb0c5bede4f7199dabb5a75d0fabeb0564) Signed-off-by: Hongxu Jia Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

classes/meta: Add DISTRO_FEATURES check for gtk+/gtk3+

2015-10-01T06:43:32+00:00

If you currently do a DISTRO_FEATURES_remove = "x11" with OE-Core, you see failures due to dependency problems. The work in resolving this was partially completed a while back. This adds in the markup mainly for gtk/gtk3+ recipes and means "bitbake world" will work successfully. Rather than code the gtk/gtk+ specific distro features into each recipe, a shared variable is used. (From OE-Core rev: ef967c70182eeccb59c7511d838a7ecb0b2315c1) Signed-off-by: Richard Purdie

default-distrovars: Clean up gcc license issues

2015-04-30T22:04:12+00:00

There are several entries here which are not needed with the modern license handling code: gcc-source - moved to direct handling in base.bbclass (due to version appended to the name) libgcc - Listed as GPLv3 exception for its packages libgcc-initial - Listed as GPLv3 exception gcc-runtime - Indivisual packages listed as GPLv3 exception where appropriate (From OE-Core rev: 48c4922ab921a1bb2103cc331d0839febd36beb8) Signed-off-by: Richard Purdie