summaryrefslogtreecommitdiffstats
path: root/meta/conf/distro/include
Commit message (Collapse)AuthorAgeFilesLines
* yocto-uninative: Update to 1.0.1 tarballFabio Berton2016-08-311-3/+3
| | | | | | | | | | The 1.0.1 uninative tarball includes the change for GlibC to use the host locale data, which is required for Python 3 to work properly. (From OE-Core rev: 4ac90c58032e1097abefc14bfc5029db0a893aa9) Signed-off-by: Fabio Berton <fabio.berton@ossystems.com.br> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* default-providers.inc: set openssl PREFERRED_PROVIDER to opensslAndre McCurdy2016-04-181-0/+3
| | | | | | | | | | | | Although the oe-core openssl recipe is currently the only provider of openssl, make the preference for using it explicit in anticipation of a libressl recipe being added to meta-oe. (From OE-Core rev: 34be80665f1edf96ccaa8f0c612464f0704ec564) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* default-providers: Update to use PREFERRED_RPROVIDERRichard Purdie2016-04-151-4/+2
| | | | | | | | | | | Get rid of the very confusing PREFERRED_PROVIDER_bluez4 using the new/better PREFERRED_RPROVIDER syntax. [YOCTO #5044] (From OE-Core rev: e5c43dc7f1e17f360b5dc762045ccf7895d18843) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* default-distrovars.inc: remove libassuan from LGPLv2_WHITELIST_GPL-3.0Andre McCurdy2016-04-031-1/+1
| | | | | | | | | | | 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 <armccurdy@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* base.bbclass: drop obsolete HOSTTOOLS_WHITELIST_GPL-3.0Andre McCurdy2016-04-011-3/+0
| | | | | | | | | | | | | 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 <armccurdy@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* default-distrovars.inc: remove gnutls + libtasn1 from LGPLv2_WHITELIST_GPL-3.0Andre McCurdy2016-03-311-1/+1
| | | | | | | | | | | | 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 <armccurdy@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* uninative: Switch md5sum -> sha256Richard Purdie2016-03-311-2/+2
| | | | | | | | There are various concerns about md5 so use sha256 instead. (From OE-Core rev: a88603cb2ffd4f995e16349a389902eb884252e5) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* no-static-libs.inc: build static libusb1-nativeMartin Jansa2016-03-291-0/+2
| | | | | | | (From OE-Core rev: c8256a88b366fdc9605e31765b4398f99520f483) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* make, remake: make them properly exclude each otherAlexander Kanavin2016-03-281-1/+2
| | | | | | | | | | Remake and make can't be installed at the same time as they're both installing a header file with the same name. (From OE-Core rev: e8747ff4c2b5830c5fa76f4c6b872da4a7d6a586) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* no-static-libs: just like target and native, nativesk-libcap doesn't like ↵Ross Burton2016-03-251-0/+1
| | | | | | | | | unrecognised options (From OE-Core rev: 79ec2ec397a35d6405f9c2b3c67e8b9981fbe7be) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* world-broken: Add packages broken on muslKhem Raj2016-03-201-0/+44
| | | | | | | | | | These 14 packages are failing aross all architectures on musl targets. (From OE-Core rev: e93f5f7c15cd46a38f2e6b1b1d96cd81880f030a) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* musl: disable building of gobject introspection dataAlexander Kanavin2016-03-121-0/+4
| | | | | | | | | When musl is in use, GLib binaries crash on assertion failures under qemu (From OE-Core rev: f69b36c2c8b77e6d991dce8fdc63887f32526d31) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python-pygtk: remove the recipeAlexander Kanavin2016-03-121-1/+0
| | | | | | | | | | | python-pygtk hasn't been updated in several years, is incompatible with the current version of pygobject, and is generally obsolete as all modern python gtk apps use introspection directly. (From OE-Core rev: 14f62d1663b7a9082b8026cd5d22eea66ad75174) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* security_flags.inc: Special flags are needed for RPMMark Hatle2016-03-091-0/+2
| | | | | | | | | | | | | | | | RPM interally has support to build and work with the stack protector. This is disabled by default in the RPM package, and the proper settings should be specified in the security_flags. Using the default setting of stack-protector-strong causes linking problems due to issues with libtool selecting the wrong GCC objections to link against. Falling back to the RPM values of stack-protector will permit linking to work properly, and some level of protection. (From OE-Core rev: 98b5f1ef188965f0116ebbe00be746dceb96936e) Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* yocto-uninative: Add common include for uninativeRichard Purdie2016-03-071-0/+11
| | | | | | | | | | uninative has some specific setup requirements. Rather than have everyone doing this themselves, do this centrally and allow people to opt into it based on some Yocto Project builds of the uninative tarballs. (From OE-Core rev: 34cf2f6be0c9b7c222d770b6af8f59addaf407b6) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* eudev: Replaces udev with eudev for compatibility when using sysvinit on ↵Alejandro Hernandez2016-03-021-1/+1
| | | | | | | | | | | | | | | | | | | newer kernels udev has started to fail on new kernels (4.4), due to being deprecated in favor of systemd's udev implementation. To maintain a sysvinit alternative we also need to provide an alternative to udev. Eudev is a fork of systemds udev, this new eudev recipe provides upstream udev 220 funcitonality. - Removes patches that dont apply anymore - ToDo: eudev-ptest? [YOCTO #8998] (From OE-Core rev: a22797f7c37a865420837b5c29b270f73ee4c6ce) Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* adt-installer: Drop since its replaced by the extensible SDKRichard Purdie2016-02-281-1/+0
| | | | | | | | | | | | | | The extensible SDK replaces adt-installer so this can be removed now, all future effort in this direction will be placed onto that. This includes a layer version change so the autobuilder knows when to stop building adt-installer. [YOCTO #6404] (From OE-Core rev: c413164c03bdce38f41e63ad2a27dc6108521b9a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* security_flags: Disable ssp when compiling uclibcKhem Raj2016-02-221-0/+4
| | | | | | | (From OE-Core rev: 208fbdbff17f19a23944a62f1b9ff380f1bc8ac8) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* glibc: Upgrade to 2.23Khem Raj2016-02-211-2/+2
| | | | | | | | | | | Drop kconfig and options-group support Forward port cross-localedef support Assume ssp support in libc when building gcc-initial (From OE-Core rev: 9c3d461c4d54d684b38ec4c038a1c3c2fb9923f0) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* no-static-libs: remove eglinfoRoss Burton2016-02-211-3/+2
| | | | | | | | | | waf.bbclass disables no-static-libs for all waf recipes, so we don't need to have it explicitly disabled here now. (From OE-Core rev: 6eb64cdd5296c42a46f3485bca403814eec55b2c) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* no-static-libs.inc: Add libcap-nativeRichard Purdie2016-02-181-0/+1
| | | | | | | | We need to disable static flags for libcap-native as well. (From OE-Core rev: b1fa25a238d118f433759102b13896094394ceeb) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* conf/no-static-libs: add explicit rule for libicalRoss Burton2016-02-161-0/+2
| | | | | | | | | | cmake doesn't have a standard for disabling static libraries so libical needs an explicit statement. (From OE-Core rev: 1a14bc0cc7f1a56833cca7baf12ed5a979854a7b) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* security_flags: Add SECURITY_CFLAGS to TARGET_CC_ARCH for binutilsKhem Raj2016-02-161-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | libtool decides to filter out -fstack-protector-strong on its own and its documented here https://www.gnu.org/software/libtool/manual/html_node/Stripped-link-flags.html this causes linking errors when linking libbfd.so since objects (.o) are compiled using -fstack-protector-strong so they are expecting to link with libssp but the option goes missing in linker flags. With this patch the security flags are hoisted upto CC itself and libtool thankfully does not touch CC. Adding to CC also means that we can now remove it from LDFLAGS since when gcc driver is used to do linking then we have LD = CC and this option makes to linker cmdline Since CC is used without CFLAGS in configure tests, some tests fail complaining that -Olevel is not used while using _FORTIFY_SOURCE therefore added SELECTED_OPTIMIZATION to TARGET_CC_ARCH as well (From OE-Core rev: 9349f28531619a4ff15c382dacc460d61e3ec7af) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* conf/distro/include: Add no-static-libs.incRichard Purdie2016-02-151-0/+30
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Static libraries are old technology. We've left them around since in previous tests, they only added around 5% to the overall build time. With new and interesting uses of OE, they're becoming more problematic. For example, sstate becomes much larger with static libs enabled which increases the size of eSDK and increases the time taken for sstate operations. Since the static libs contain all the debugging symbols, they're also pretty huge. This patch adds a common include file which allows the user or distro to disable the static libraries in the majority of cases. There are some libs where we do need the static lib, a good example being pseudo-native which uses sqlite3-native static libs. These are left enabled by the include file, as are recipes where --disable-static doesn't work, or isn't supported. This list can likely be reduced over time as individual corner cases are addressed. Maintaining this list in a common location is more desireable than everyone doing it themselves. Poky will switch to using this, OE-Core will need to discuss that as its default. (From OE-Core rev: 773c9e18071d71454473dd81aff911104a2e9bc6) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* security_flags: wipe security flags for gcc/glibc and related librariesKhem Raj2016-02-071-3/+8
| | | | | | | | | | | It causes a catch-22 situation where we build libssp in gcc-runtime but also pass -fstack-protector flags which require libssp (From OE-Core rev: 61ef8212cc6880f502f1e05e2683d232ea782ae4) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* security_flags: use -fstack-protector-strongKhem Raj2016-02-071-5/+5
| | | | | | | | | | | | | | | This is a better version of -fstack-protector-all with reduced stack usage and better performance yet giving same amount of coverage. It's available in gcc 4.9 onwards. https://outflux.net/blog/archives/2014/01/27/fstack-protector-strong/ has more details. (From OE-Core rev: 4ca946c029f04ba3991ed0f1f65355a7a7840ff4) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* security_flags: ensure security flags only apply to target buildsKhem Raj2016-02-071-2/+2
| | | | | | | | | | | As otherwise the security flags can leak into target builds. This can result in flags that the host compiler doesn't support, causing build failures. (From OE-Core rev: ff2c8af73046f55aa733ce8289b6236c88300290) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* security_flags.inc: don't do -pie for syslinuxRoss Burton2016-02-071-0/+1
| | | | | | | | | | | sysroots/x86_64-linux/usr/libexec/x86_64-poky-linux/gcc/x86_64-poky-linux/5.3.0/ld: syslinux.o: relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making a shared object; recompile with -fPIC (From OE-Core rev: b87a9c82663446fa8c002e144de57127e8902b54) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gtk-theme-torturer: remove from oe-coreRoss Burton2016-02-061-1/+0
| | | | | | | | | | | This recipe is very old, unmaintained, not used at all in OE-Core, and not useful in a world that has moved to GTK+ 3 (even if Sato is slow at catching up). (From OE-Core rev: d9ecac4828cb316230c3681670e7bf6d197e3a30) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* binutils: Upgrade to 2.26Khem Raj2016-02-011-1/+1
| | | | | | | (From OE-Core rev: 86ade2cc2553c942d9526c5323a11ae151653505) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libc-package.bbclass: add LOCALE_UTF8_IS_DEFAULTRichard Tollerton2016-01-301-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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 <rich.tollerton@ni.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-libc-headers: update to 4.4Bruce Ashfield2016-01-241-1/+1
| | | | | | | | | | Updating the lib-headers to match the 4.4 LTSI kernel version. (From OE-Core rev: 046b1f4cf439e36c8e8a4904f8e8014a9ea733e2) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python: Upgrade 2.7.9 > 2.7.11Alejandro Hernandez2016-01-201-2/+2
| | | | | | | | | | | | | - no license change, just dates Rebased: - check-if-target-is-64b-not-host.patch - add-CROSSPYTHONPATH-for-PYTHON_FOR_BUILD.patch (From OE-Core rev: 9ed4ef038a4a8140accfa97b2eb6b75f8bed3693) Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* security_flags.inc: remove obsolete workarounds for curlAndre McCurdy2016-01-191-4/+0
| | | | | | | | | | | | | | | | | | | | | | The curl configure script contains sanity checks for unexpected options being passed via CFLAGS, LDFLAGS, etc. environment variables. These sanity checks catch -Dxxx options in CFLAGS, which clashes with OE's approach of using CFLAGS to pass -D_FORTIFY_SOURCE (curl's configure script suggests, quite correctly, that -Dxxx options should be passed via CPPFLAGS instead). These sanity checks previously generated fatal errors, but have been downgraded to warnings since curl v7.32. Therefore the workaround of avoiding -D_FORTIFY_SOURCE for curl is obsolete and can be removed. https://github.com/bagder/curl/commit/5d3cbde72ece7d83c280492957a26e26ab4e5cca (From OE-Core rev: d0dfd7bf9b2d6fb269f4d9b62263fd7ccc805fde) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tcmode-default.inc: Fix preferred provider nativesdk-sdk_prefix-libc-initialMark Hatle2016-01-151-1/+1
| | | | | | | | | | | Similar to the libc-for-gcc preferred provider, we also need a libc-initial version. Layers such as meta-mingw need the ability to override these values in order to generate an SDK that works on non Linux environments. (From OE-Core rev: ea4b19ad2e4d259c41c9e09ecb70bc8043509a4f) Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gdb: upgrade to 7.10.1Richard Purdie2016-01-151-1/+1
| | | | | | | | | The PPC inferior patch was dropped since an equivalent fix was merged upstream. (From OE-Core rev: 564c56207edd9a7dcef3ea966580e11a1548115c) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* x11vnc: remove all references to moved packageIoan-Adrian Ratiu2016-01-071-1/+0
| | | | | | | | | | | | Together with the move to meta-oe, all references to x11vnc should be removed from oe-core. There are three of these: a distro alias, a packagegroup rdepends and a runtime test. (From OE-Core rev: cfd1e4bcd66a9a542007115647cadb8480330fab) Signed-off-by: Ioan-Adrian Ratiu <adrian.ratiu@ni.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* security_flags.inc: disable -fstack-protector-XXX for valgrindAndre McCurdy2016-01-071-1/+1
| | | | | | | | | | | | | | | | | Valgrind (v3.11.0) expects to build with stack protection disabled and includes -fno-stack-protector in its default CFLAGS. However, the CFLAGS provided by OE are included on the compiler command line after the defaults so any -fstack-protector-all / -fstack-protector-strong option provided by security_flags.inc will cause problems. | .../build-bcm97425vms/tmp/work/mips32el-rdk-linux/valgrind/3.11.0-r0/valgrind-3.11.0/coregrind/m_mallocfree.c:892: undefined reference to `__stack_chk_guard' | .../build-bcm97425vms/tmp/work/mips32el-rdk-linux/valgrind/3.11.0-r0/valgrind-3.11.0/coregrind/m_mallocfree.c:947: undefined reference to `__stack_chk_fail' (From OE-Core rev: ff4f46700a4810fcb49c58978b17af4f52fa9925) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qt4: remove recipes and classesAlexander Kanavin2016-01-072-22/+0
| | | | | | | | | | | | 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 <alexander.kanavin@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* base-utils:flexible dependency for command utilitiesAlejandro Joya2016-01-061-0/+3
| | | | | | | | | | add base-line configuration for command utilities, this will be used instead of hardcoded uses of busybox around the environment. (From OE-Core rev: b14027e361fc0393fa4ee060ecb1088742607533) Signed-off-by: Alejandro Joya <alejandro.joya.cruz@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tcmode-default: Use glibc for nativesdk version even on uclibc and muslKhem Raj2015-12-281-2/+2
| | | | | | | | | | | | We do not have musl or uclibc based systems for building OE itself. Most of build servers run glibc, there will be other issues to build OE on a uclibc based build system (From OE-Core rev: 3ec457e7cdc347a98ab561fd3d2a500a218cdeb0) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* uclibc: Switch to using uclibc-ngKhem Raj2015-12-161-1/+1
| | | | | | | | | | | uclibc-ng is a maintained fork of uclibc project. Lets switch to using that add patches to fix memory leak in canonicalize_file_name-memory (From OE-Core rev: 6a4996395f56836195f5ba10a554ba04eb304c13) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* package_regex.inc: split the rest of the entries to their recipesAlexander Kanavin2015-12-081-68/+0
| | | | | | | | (From OE-Core rev: 73e2555cc7d529a93362b3fcfea3fbc7a4c60ca1) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* package_regex.inc: split entries which blacklist specific versions to their ↵Alexander Kanavin2015-12-081-35/+0
| | | | | | | | | | recipes (From OE-Core rev: 1eb9e190ef3bb1170b3eaabd9f7900e7ce176624) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* package_regex.inc: split sourceforge related entries to their own recipesAlexander Kanavin2015-12-081-43/+0
| | | | | | | | (From OE-Core rev: 4c5899fa0b8258f2754e3080dae5535e3b248e91) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* package_regex.inc: split PyPi related entries to their own recipesAlexander Kanavin2015-12-081-19/+0
| | | | | | | | (From OE-Core rev: 9528cff2ecf4241cb80d9e972751d7ac607d39e4) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* package_regex.inc: split Debian-related entries into their own recipesAlexander Kanavin2015-12-081-17/+0
| | | | | | | | (From OE-Core rev: 2a5e1848c11bd9a3c64cf8fcc0cb334c738bc5c5) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* package_regex.inc: split GITTAGREGEX entries into recipe filesAlexander Kanavin2015-12-081-26/+0
| | | | | | | | (From OE-Core rev: 589f5442372a7ab0f8bc40403e1739ce1cdd1cc0) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* package_regex.inc: split entries with odd-even versioning into their own recipesAlexander Kanavin2015-12-081-51/+0
| | | | | | | | (From OE-Core rev: 5ddaba1fb833d0408cef5f58f786513b9293c30a) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* package_regex.inc: deprecate the fileAlexander Kanavin2015-12-081-4/+6
| | | | | | | | | | | New entries should be added to recipes themselves. Also update the comment to reflect the new variable names. (From OE-Core rev: 452b196565c1f19bb736ce4debae576b2f5420aa) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-11-16 02:36:55 +0000