summaryrefslogtreecommitdiff
path: root/meta/conf/distro/include/default-providers.inc
AgeCommit message (Collapse)AuthorFiles
2016-04-18default-providers.inc: set openssl PREFERRED_PROVIDER to opensslAndre McCurdy1
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. Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2016-04-15default-providers: Update to use PREFERRED_RPROVIDERRichard Purdie1
Get rid of the very confusing PREFERRED_PROVIDER_bluez4 using the new/better PREFERRED_RPROVIDER syntax. [YOCTO #5044] Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-03-26make, remake: make them properly exclude each otherAlexander Kanavin1
Remake and make can't be installed at the same time as they're both installing a header file with the same name. Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-03-02eudev: Replaces udev with eudev for compatibility when using sysvinit on ↵Alejandro Hernandez1
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] Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-01-05base-utils:flexible dependency for command utilitiesAlejandro Joya1
add base-line configuration for command utilities, this will be used instead of hardcoded uses of busybox around the environment. Signed-off-by: Alejandro Joya <alejandro.joya.cruz@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-08-31packagegroup-base: pull in iw as well as wireless-toolsChristopher Larson1
As was discussed in the commit which adds iw: iw uses cfg80211/nl80211, which is the way of the future. wireless-tools uses WEXT, which uses ioctl, which is in deep maintenance mode. See http://wireless.kernel.org/en/developers/Documentation/Wireless-Extensions. Also https://wireless.wiki.kernel.org/en/users/Documentation/iw indicates "The old tool iwconfing, which uses Wireless Extensions interface, is deprecated and it's strongly recommended to switch to iw and nl80211." wireless-tools is kept as well for now for compatibility reasons, until we have verified that all the network configuration mechanisms are using iw. This adds VIRTUAL-RUNTIME_wireless-tools as a distro convenience. Signed-off-by: Christopher Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-02-17default-providers: Set the preferred provider for bluez based on versionRichard Purdie1
bitbake will currently 'selecting bluez4 to satisfy runtime libasound-module-bluez due to PREFERRED_PROVIDER_bluez4 = bluez4' which in the case of bluez5 isn't correct. This slightly unusual construct avoids this. Ultimately this is a bitbake issue that needs fixing in a better way but this means we can merge the bluez5 changes until bitbake gets fixed. Signed-off-by: Cristian Iorga <cristian.iorga@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-02-17conf/distro/include/default-providers: updated bluez-hcidump providersCristian Iorga1
If BlueZ5 is added to a build as a replacement for BlueZ4, the provider for bluez-hcidump will be bluez5. Signed-off-by: Cristian Iorga <cristian.iorga@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-12-11bluez-hcidump: select provider as bluez4 or bluez5Peter A. Bigot1
bluez-hcidump was a separate package in bluez4, but was integrated into bluez5. Signed-off-by: Peter A. Bigot <pab@pabigot.com>
2014-11-20default-providers.inc: define VIRTUAL-RUNTIME_getoptRichard Tollerton1
getopt can be provided by either util-linux or busybox. Allow the distro to control which implementation is used, and default it to util-linux. Signed-off-by: Richard Tollerton <rich.tollerton@ni.com> Acked-by: Ken Sharp <ken.sharp@ni.com> Acked-by: Ben Shelton <ben.shelton@ni.com Acked-by: Brad Mouring <brad.mouring@ni.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2014-04-25Globally replace 'base_contains' calls with 'bb.utils.contains'Otavio Salvador1
The base_contains is kept as a compatibility method and we ought to not use it in OE-Core so we can remove it from base metadata in future. Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-01-16default-providers: Change update-alternatives provider to opkg-utilsPaul Barker1
This allows dependencies to be added to the opkg recipe without causing circular dependency loops. As opkg-utils has minimal dependencies it is the best recipe to provide update-alternatives. This partially solves Yocto Project issue 4836. More work is still needed for a complete solution. Signed-off-by: Paul Barker <paul@paulbarker.me.uk> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-12-10ltp: set PREFERRED_PROVIDER and rename runtests_noltp.sh scriptMartin Jansa1
* ltp installs 2 different runtests_noltp.sh files from different directories into /opt/ltp/testcases/bin/runtests_noltp.sh last one installed wins and causes unexpected changes in buildhistory's files-in-image.txt report, rename them to have unique name as other ltp scripts have. * also define PREFERRED_PROVIDER to resolve note shown when building with meta-oe layer: NOTE: multiple providers are available for ltp (ltp, ltp-ddt) NOTE: consider defining a PREFERRED_PROVIDER entry to match ltp Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-09-17mesa: add virtual/mesa providerRoss Burton1
As there are two alternative mesa recipes (mesa and mesa-gl), there needs to be a virtual provider that recipes that explicitly need Mesa (such as xserver-xorg) can depend on. Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-08-23default-providers: Set the preferred provider for bluezCristian Iorga1
There is a need for a default provider for bluez now that bluez5 recipe is also present. After the introduction of bluez5 recipe, the following warnings are displayed: "NOTE: multiple providers are available for runtime libasound-module-bluez (bluez4, bluez5) NOTE: consider defining a PREFERRED_PROVIDER entry to match libasound-module-bluez" Upon debug, bitbake shows: DEBUG: checking PREFERRED_PROVIDER_bluez4 (value None) against ['bluez4', 'bluez5'] DEBUG: checking PREFERRED_PROVIDER_bluez4-4.101 (value None) against ['bluez4', 'bluez5'] DEBUG: checking PREFERRED_PROVIDER_bluez4-4.101-r5 (value None) against ['bluez4', 'bluez5'] DEBUG: checking PREFERRED_PROVIDER_bluez5 (value None) against ['bluez4', 'bluez5'] DEBUG: checking PREFERRED_PROVIDER_bluez5-5.7 (value None) against ['bluez4', 'bluez5'] DEBUG: checking PREFERRED_PROVIDER_bluez5-5.7-r0 (value None) against ['bluez4', 'bluez5'] Bitbake is faced with the question "what should provide libasound-module-bluez?" which is a runtime name. It needs to try and find a PREFERRED_PROVIDER entry which matches this but those use *build time* naming. So it converts "libasound-module-bluez" into the canonical ${PN} of bluez4 and bluez5 and then tries to look those up. What it actually should do is go one step further of mapping bluez4/bluez5 into the virtual/bluez but that does not happen. Bug opened on this issue: YB5044 https://bugzilla.yoctoproject.org/show_bug.cgi?id=5044 [YOCTO #5030] Signed-off-by: Cristian Iorga <cristian.iorga@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-08-16qemu, default-providers: Add mesa as default virtual/eglMartin Jansa1
* it's safer to select it consistently with virtual/libgl* providers Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-04-02remove gtk-update-icon-cache-native virtualsAndreas Müller1
gtk-update-icon-cache-native is the only provider now Signed-off-by: Andreas Müller <schnitzeltony@googlemail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-03-26default-providers: change udev selection logicRoss Burton1
Change the logic so that the udev provider is the standalone udev, unless the systemd DISTRO_FEATURE is set. The previous logic was designed to fail if both sysvinit and systemd were enabled, which we're supporting now. Signed-off-by: Ross Burton <ross.burton@intel.com>
2013-03-22mesa: rename mesa-dri recipe to just mesaLaurentiu Palcu1
Rename mesa-dri recipes to just mesa. Also, replace all references to mesa-dri in all recipes/configs. The reason for this renaming (quote from bugzilla): "mesa-dri is a artefact of mesa-xlib existing, which doesn't anymore. mesa-dri should be renamed to mesa." [YOCTO #3385] Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-03-05default-providers: add default virtual provider for gtk-update-icon-cacheRoss Burton1
Use a virtual provider instead of a hard dependency so that if gtk+-native is required in some configuration, this provider can be changed and then gtk+-native and gtk-update-icon-cache-native won't be both built and conflict in the sysroot. Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-01-20update-alternatives: Add a build-time dependencyMark Hatle1
We need to add a build time dependency on virtual/update-alternatives, however we can't just do DEPENDS +=, or we end up with various problems. To work around this, in the anonymous python space we ensure we only do the addition when the package does not provide virtual/update-alternatives and it is a target package. Also the system wide PREFERRED_PROVIDER was incorrect. It references a runtime package, and not the recipe it should have. This has been corrected. [YOCTO #3691] Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Tested-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-01-20default-providers: Add systemd option to PREFERRED_PROVIDER_udevRadu Moisan1
Signed-off-by: Radu Moisan <radu.moisan@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-01-20default-providers: Automatically set PREFERRED_PROVIDER_udevRadu Moisan1
This is a more generic way to set preferred provider for udev. We expect to have multiple choices once we integrate other init managers, and this way we can automatically set it considering distro settings. Signed-off-by: Radu Moisan <radu.moisan@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-11-18default-providers: add default provider for makeRoss Burton1
remake PROVIDES make, so we need a default provider. Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-09-12default-providers: default to libx11, not -trimRoss Burton1
Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-08-31nativesdk: Switch to using nativesdk as a prefix, not a suffixRichard Purdie1
As discussed on the mailing lists, using a suffix to package names is hard and has lead to many recipes having to do PKGSUFFIX games. Its looking extremely hard to scale nativesdk much further without hacking many recipes. By comparison, using a prefix like multilib does works much better and doesn't involve "hacking" as many recipes. This change converts nativesdk to use a prefix using the existing multilib infrastructure. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-08-19core: Prefer mesa-dri as virtual/libopengles1/2 providerDamien Lespiau1
Wihtout it, you have both mesa-dri and mesa-xlib as providers. Let's prefer the accelerated version. Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2012-03-19default-providers: Set pigz-native as the default provider for gzip-nativeRichard Purdie1
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-02-01default-providers: add kbd as PREFERRED_PROVIDER for console-toolsSaul Wold1
kbd is used a primary provider for console-tools Signed-off-by: Saul Wold <sgw@linux.intel.com>
2012-01-19task-base: rename VIRTUAL-RUNTIME-alsa-state to use underscoreMartin Jansa1
* in http://lists.linuxtogo.org/pipermail/openembedded-core/2012-January/016226.html we talked about VIRTUAL-RUNTIME_alsa-state, but VIRTUAL-RUNTIME-alsa-state was used instead, which is inconsistent with other VIRTUAL-RUNTIME vars Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-01-17task-base: add VIRTUAL-RUNTIME_alsa-state to task-base-alsaJoshua Lock1
Define this to be the alsa-state package by default. This enables automatic configuration setting and restoration on systems with alsa. Signed-off-by: Joshua Lock <josh@linux.intel.com>
2012-01-17task-base: move default definition of VIRTUAL-RUNTIME_apmJoshua Lock1
This belongs in default-providers.conf Signed-off-by: Joshua Lock <josh@linux.intel.com>
2011-11-10gconf: add upstream GNOME gconf 3.2.3 and drop gconf-dbusJoshua Lock1
The D-Bus backend has been integrated into upstream GConf so we can switch to upstream and drop gconf-dbus. I've gone for a release in the 3.2 series as we disable Gtk+, and therefore are not impacted by the gtk+3 changes, and the D-Bus backend was unstable before this release. Signed-off-by: Joshua Lock <josh@linux.intel.com>
2011-10-24default-providers: switch virtual/libgl from mesa-xlib to mesa-driMartin Jansa1
* to match default virtual/xserver Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2011-10-17default-provider: also define a default provider for gconf-nativeDmitry Eremin-Solenikov1
Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-10-11xserver-xf86(-dri)-lite: rename to xserver-xorg and xserver-xorg-liteMartin Jansa1
* xserver-xorg is closer to upstream naming and that's how it's named in OE-classic and meta-oe? It would make meta-oe transition easier and better to do it now then convert meta-oe to xserver-xf86 and then rename it back later. Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2011-05-11bitbake.conf: Include the new default-providers.inc and default-versions.inc ↵Richard Purdie1
files These are the minimal defaults to allow OE-Core to function standalone with no distro set and are constucted such that the distro can either override values, or totally replace the include file entirely as needed. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-16 20:55:12 +0000