aboutsummaryrefslogtreecommitdiffstats
path: root/meta/recipes-devtools/opkg
AgeCommit message (Collapse)Author
2014-07-08opkg: putting the service files into PNRoy Li
(From OE-Core rev: f0ec7f81c1951211f049c342fd6bd1cad424564a) [YOCTO #6392] (From OE-Core rev: b76a5dd195000d157034f1f0a9a35d4ba4680e60) Signed-off-by: Roy Li <rongqing.li@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-12-12systemd-compat-units: run-postinsts fix script linkAndreas Müller
in commit fe039170236080291c0220476a5809774f82ee5c Author: Muhammad Shakeel <muhammad_shakeel@mentor.com> Date: Wed Oct 2 10:55:32 2013 +0000 systemd-compat-units: Use correct run-postinsts script link OE-Core commit 75a14923da1ba91eddde47f0907345c19c82d6f0 has moved run-postinsts script execution from S98 to S99 in rcS.d. run-postinsts.service should check for this script and run it on first boot rather than S98run-postinsts, which is for opkg/dpkg. the link was corrected but the mentioned commit is not available. Instead of reverting, we use the same variable as opkg for init script ordering and drop a note in case somebody wants to change default. (From OE-Core master rev: 7aabc9408fb382f0ae39f9932b6d9ac391528b76) (From OE-Core rev: 91a51e10392c0f802d6c329ad2b11ae82c55f171) Signed-off-by: Andreas Müller <schnitzeltony@googlemail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-10-04opkg: ignore result of opkg configureMuhammad Shakeel
Some packages may return error while running opkg-cl configure, during first boot. This will fail 'ExecStart' and 'ExecStartPost' will not run. Without 'ExecStartPost' opkg-configure service will continue to run on successive boot attempts. 'ExecStartPost' should disable this service after first boot irrespective of 'ExecStart' status. (From OE-Core rev: cd6041071ddf76693cda7632379ceddd1d21a7fb) Signed-off-by: Muhammad Shakeel <muhammad_shakeel@mentor.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-09-30opkg: Use systemd service for first boot configurationMuhammad Shakeel
Currently opkg uses a script to configure packages during first time boot. This script is present in rcS.d and when 'sysvinit' is disabled this script doesn't execute. For systemd only distros this newly added service will run the opkg configure during first boot only. (From OE-Core rev: fdcfcea5b8eae1769a217f8efea9c02f037f63fa) Signed-off-by: Muhammad Shakeel <muhammad_shakeel@mentor.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-08-26opkg: add missing initialization of conf->exclude_listJonathan Liu
(From OE-Core rev: e4190b601c0212f0009ddb2dfa00d2880bddbc29) Signed-off-by: Jonathan Liu <net147@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-08-22opkg: Add support for excluding packages from the installMark Hatle
This adds a new argument to opkg-cl, --add-exclude, which is used to add package names to the list of packages to exclude from the install. If an excluded package is needed for the install to resolve, an error will be generated. Recommended packages will not generate an error. (From OE-Core rev: 63c61b7c0c8aeb89661e3bb85e281dd1ef5b618c) Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-08-22opkg: Add --no-install-recommends option.Mark Hatle
The new --no-install-recommends option is similar to the behavior of apt-get's --no-install-recommedns. Only required packages will be installed. (From OE-Core rev: 86a30a88cf89ed97c372c391169f4ae243c89fd2) Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-08-16opkg.inc: remove the obsolete POSTLOG variableChen Qi
With the current implementation of postinst logging mechanism, the location for log file is configured via the POSTINST_LOGFILE variable. The POSTLOG variable is obsolete now, thus removing it. (From OE-Core rev: 6aaf2d5c51eb4ee6acbb85fd4aa5f44406907bc2) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-08-13opkg: Fix possible installation of GPLv3 headerPaul Barker
opkg is GPLv2+ licensed but it has optional support for sha256 checksums which was GPLv3+ licensed. This code is not built unless '--enable-sha256' is passed to the configure script, the default is equivalent to '--disable-sha256'. However, the header 'sha256.h', which is GPLv3+ licensed, is in the list of header files to be installed and thus could end up in the libopkg-dev package. As this header is installed to '/usr/include/libopkg' it is very unlikely that it will ever be used. However, if you're uncomfortable with GPLv3 code going anywhere near your target filesystem you won't want this to happen. The simplest solution is to replace the sha256 implementation in opkg with the implementation from coreutils-6.9 which is licensed under GPLv2+. This is committed to the opkg subversion repository as r652/r653. The only intervening commit between r650 (previous SRCREV) and this is r651, which integrates 'obsolete_automake_macros.patch' into the opkg sources. Thus this patch isn't needed in oe-core anymore. (Note: Before 873689bbabba25e7be5c12317c04519a7bc8d0ef, this header is only installed if opkg is built in its source tree (ie. ${B}=${S}). After that commit the header will always be installed) (From OE-Core rev: 3c6a8a39d820f14f9eb3df3d719cef2c469769da) Signed-off-by: Paul Barker <paul@paulbarker.me.uk> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-08-03opkg: Bump SRCREV as patch has been applied upstreamPaul Barker
The previous patch to fix the installation of libopkg headers has been accepted upstream and is the next commit after the SRCREV used by the opkg recipe. Therefore the patch can be replaced by a simple update of the SRCREV. (From OE-Core rev: e14df11795a03da4bb36f5172edbf9ca7e8ba681) Signed-off-by: Paul Barker <paul@paulbarker.me.uk> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-08-03opkg.inc: remove the obsolete REDIRECT_CMDChen Qi
The REDIRECT_CMD variable is now obsolete, remove it. (From OE-Core rev: cba8f3257bb645dafdfa7c672bbdc4b0f0c094e6) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-07-18Upstream-Status: Correct capitalizationSaul Wold
(From OE-Core rev: 2d5c457bf888771891e9c29e82ec5a5cecace528) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-06-18opkg: put libopkg header files into libopkg-devPaul Barker
The header files for libopkg belong in the package libopkg-dev rather than opkg-dev where they are placed by default. (From OE-Core rev: f79cd4208340b56afc044d8e3abc72d43d395062) Signed-off-by: Paul Barker <paul@paulbarker.me.uk> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-06-18opkg: fix header installation for libopkgPaul Barker
When opkg is built outside the source directory, libopkg headers aren't all installed as the search path for headers only includes the directory that make is being ran in, not the source directory. So we fix this by adding $(srcdir)/*.h to the list of header files to install. Without this patch, "/usr/include/libopkg" will only include the file config.h. With this patch, other files such as "opkg.h" are present which are needed to compile software which uses libopkg. The new patch has also been submitted upstream as a fix to opkg itself. (From OE-Core rev: 873689bbabba25e7be5c12317c04519a7bc8d0ef) Signed-off-by: Paul Barker <paul@paulbarker.me.uk> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-05-23opkg: modify the run-postinst script to enable postinst loggingChen Qi
Enable postinst logging by checking the configuration in ${sysconfdir} /default/postinst. In this way, the postinst logging is enabled if 'debug-tweaks' is in IMAGE_FEATURES, and at the same time, we avoid unnecessary rebuilt if IMAGE_FEATURES is changed. [YOCTO #4262] (From OE-Core rev: 35be6ffc19a5156aa029397707f1e6869684b821) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-05-21opkg: remove unnecessary extra leading slash in run-postinstsJonathan Liu
(From OE-Core rev: 047826f034f00c2402c0a078b5c918019fcf36a4) Signed-off-by: Jonathan Liu <net147@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-11opkg.inc: don't hardcode /var/lib/opkgLaurentiu Palcu
(From OE-Core rev: 9caf1f2540f0419c1301cc21777f97c6671fd844) Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-11dpkg, opkg, rpm-postinsts: avoid repackaging when changing IMAGE_FEATURESPaul Eggleton
Recipes cannot depend on the value of IMAGE_FEATURES; in this case the result is do_package task signatures changing every time IMAGE_FEATURES changes, causing a large number of task re-executions. The implementation of the log capturing really needs to be changed to capture these in a different place and possibly not even conditional upon IMAGE_FEATURES at all, but this will be invasive at this point in the development cycle. For now, remove the variable dependencies to fix the immediate problem. Fixes [YOCTO #4246]. (From OE-Core rev: b4fbe4095de447ef4e426128bafaf8a292fa63e1) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-11dpkg, opkg, rpm-postinst: fix overwriting the run-postinstall scriptLaurentiu Palcu
If multiple package managers are installed in the image, they will overwrite each other's run-postinsts script, resulting in postinstalls not beeing run at all at first boot. What this patch does: * checks whether opkg/dpks/rpm is actually used to install the packages and, only after, creates the run-postinsts script; * brings dpkg recipe in sync with opkg: moves the script creation from do_install to postinstall; * move creation of run-postinsts script (rpm-postinsts recipe) to the postinstall scriptlet in order to better control the creation of the script according to the package manager used; [YOCTO #4231] [YOCTO #4179] (From OE-Core rev: d7fd56df0a4954954d6d0764ae06beb869e6b99a) Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-03-07opkg: save output of postinst scripts when image first bootKang Kai
When image feature "debug-tweaks" enabled, save output of postinstall scripts to log file /var/log/postinstall.log when image first boot. And the log file can be configured. It also needs image feature "package-management" enabled. If not, package run-postinsts will be installed and then all packages will be configured by it. Command 'opkg configure' outputs nothing. [YOCTO #3223] (From OE-Core rev: 378504c1c0ab1e0e09950b37effc04221b928236) Signed-off-by: Kang Kai <kai.kang@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-02-06opkg: replace obsolete automake macros with working onesMarko Lindqvist
Add obsolete_automake_macros.patch that replaces automake macros no longer supported by automake-1.13 with modern constructs. (From OE-Core rev: 495bea3911be164225c91b696389fc16dab356fd) Signed-off-by: Marko Lindqvist <cazfi74@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-02-06ipk: use OPKGLIBDIR in all placesMartin Jansa
* it's not recommended to change this value, because it breaks upgrade path on target (all old u-a alternatives are forgot in old OPKGLIBDIR value * but make it consistent, so if someone really want to change that, then setting OPKGLIBDIR_distro in distro.conf would be enough * without this there were at least 4 places to change: rootfs_ipk: opkglibdir variable (notice that I've removed /opkg from it to correspond with EXTRA_OECONF option used in opkg recipes package_ipk: ${target_rootfs}${localstatedir}/lib/opkg/ hardcoded in package_install_internal_ipk opkg-collateral: value in lists file opkg: EXTRA_OECONF for all 3 classes, FILES_libopkg, do_install * validated with buildhistory that without OPKGLIBDIR explicitly set the output is the same and that after setting OPKGLIBDIR_forcevariable := "${libdir}" everything including empty directory from package_ipk is moved to libdir (From OE-Core rev: cf0aa9c4fdae8855803e96b1922d54a2431795d3) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-01-07opkg-native: obey virtual/update-alternatives-nativeChristopher Larson
(From OE-Core rev: 1f9d979ca60eca2277f53f24dc59f9ab18e81195) Signed-off-by: Christopher Larson <chris_larson@mentor.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-11-24opkg: bump SRCREV and drop applied patchesMartin Jansa
* only change upstream which wasn't in oe-core is http://code.google.com/p/opkg/source/detail?r=635 and added testcase for that (From OE-Core rev: 5fd1d515db5966f45a3b2f936f3c4225f59186e2) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-11-21opkg: Drop unnecessary FILESDIR settingRichard Purdie
(From OE-Core rev: e869731f80d8c0059b44a7029543b8943fd07653) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-11-21opkg: drop PACKAGE_ARCH setting for update-alternatives-cworthMartin Jansa
* there is warning about update-alternatives-cworth ipk being overwritten in "all" feed when opkg is built for more architectures * see https://bugzilla.yoctoproject.org/show_bug.cgi?id=3390 for details (From OE-Core rev: 969d10d0aa5537a119ed9be9e8321dbd73d160fe) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-11-18opkg: added alternatives-ln patchEnrico Scholz
Use 'ln -n' to avoid dereferencing links to host files. (From OE-Core rev: e5aef500e11cbf7d1cd20b588fcea2c5fd6b5d0e) Signed-off-by: Enrico Scholz <enrico.scholz@sigma-chemnitz.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-11-02recipes-devtools: replace virtclass-native(sdk) with class-native(sdk)Robert Yang
The overrides virtclass-native and virtclass-nativesdk are deprecated, which should be replaced by class-native and class-nativesdk. [YOCTO #3297] (From OE-Core rev: bb67ddeb2eed3e25c626a279ef53a7e8c7bfe6f2) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-10-23opkg: Don't print empty PROVIDESAndrei Gherzan
Every package provides itself. While printing package information all fields are printed only if there is any relevant info for them. For example: a package with no "Replaces" won't get this printed at all. Packages which provide only themselves, were printing this field but with no values. This patch skips this field if the package provides only itself. (From OE-Core rev: 19af022c73ebc53f7008a016c1e7c584fb7b0054) Signed-off-by: Andrei Gherzan <andrei@gherzan.ro> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-10-23opkg: Add patch to fix removing packages with recommendsAndrei Gherzan
While removing a package with opkg, the process shouldn't be blocked if another package RECOMMENDS the package wanted to be removed. This is because, while generating the dependencies, opkg adds dependencies to depended_upon_by even if dependency's type is RECOMMEND. The fix is to skip dependencies of type RECOMMEND while constructing depended_upon_by. [YOCTO: #2431] (From OE-Core rev: 08a5ef44c7aa58ffcad0457e8dda3504f2c3192b) Signed-off-by: Andrei Gherzan <andrei@gherzan.ro> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-10-02opkg: Convert select-higher-version option to prefer-arch-to-versionRichard Purdie
This converts the option to maintain the existing behaviour unless the option is specified. We do specify the option during the builds themselves to ensure what the users expects is built. (From OE-Core rev: 0cc479699fe885049625d54c712b500c1b719e75) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-10-02opkg: Drop nogpg version since the main version now has nogpg tooRichard Purdie
(From OE-Core rev: c8197c993c5848576a9c63660ff342571d31a4ba) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-10-02opkg-native: remove spurious dependency on curl-nativePhil Blundell
All variants of opkg are currently configured --disable-curl so there seems no point in depending on it. (From OE-Core rev: 875f1eb876c17c038a77bc7b7a5fed775d9fd3ea) Signed-off-by: Phil Blundell <philb@gnu.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-10-02opkg: Don't call sync() when installing into an offline rootPhil Blundell
Even when installing onto a live target system, calling sync() during package installation is of somewhat questionable benefit. But calling it on the build host during rootfs construction is certainly useless and can cause I/O to stall for several seconds on even a moderately sized host which is clearly not desirable. (From a patch originally by Mike Crowe.) (From OE-Core rev: f48a68177510e8f2d4fcc3725a6dfc41a9a8e96b) Signed-off-by: Phil Blundell <philb@gnu.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-10-02opkg: fix version constraints in conflicts, depends, replacesMartin Jansa
* http://code.google.com/p/opkg/issues/detail?id=94 (From OE-Core rev: 7ebce895a215b31cf01aea2ac43e554f96ef814f) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-09-21opkg svn: respect to the arch priorityRobert Yang
This is for fixing the problem: 1) bitbake core-image-sato-sdk with MACHINE=qemux86 2) bitbake core-image-sato with with MACHINE=crownbay The qemux86's PACKAGE_ARCH is i586, the crownbay's is core2, but several i586 packages will be installed into crownbay's rootfs though there are core2 packages. For example, there are: xserver-xorg*_1.11.2-r7_i586.ipk xserver-xorg*_1.9.3-r1_core2.ipk The crownbay.conf says: PREFERRED_VERSION_xserver-xorg ?= "1.9.3" What the crownbay's image needs is xserver-xorg*_1.9.3-r1_core2.ipk, but the xserver-xorg*_1.11.2-r7_i586.ipk will be installed, this is incorrect. This is caused by opkg's selecting mechanism: when more than one candidate is found, it will use the higher version one and ignore the arch priority. we have several conf files which set the PREFERRED_VERSION_pkg = "..." , but there is no such a mechanism which can let us tell the opkg to install the preferred version. When the preferred version is higher, this is OK, but if the preferred version is lower, there would be problems: 1) Most of the packages are core2 in the image, but several of them are i586, though we have built the core2 ones, this seems strange. 2) What's worse is that the image may not work since the preferred version pkg is not installed. We have set the arch priority clearly in the opkg.conf, I think that respect to the arch priority is reasonable during the image generation. Add the "--select-higher-version" option to let the user have another choice, the default is no. [YOCTO #2575] (From OE-Core rev: 0a80a02644f624443cef8cc4f604edb5ef8e6975) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-09-21opkg-nogpg: drop SRCREVMartin Jansa
* use SRCREV from opkg_svn.bb, because with 596 patches we have won't apply (From OE-Core rev: 2bf865a9b89eb88c3f7c754362315841195cd8ca) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-09-21opkg: add patch to fix SIGSEGV when printing status fileMartin Jansa
* it was triggered by c02364f36e228835ea5d7fd4e1d347fd451f8544 when new package had 2 entries in Provides and old version just 1 (From OE-Core rev: d98d6ec9425bd8764405c9812cddfcfd2a2b025b) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-09-21opkg: replace local patches with git patches submitted upstreamMartin Jansa
(From OE-Core rev: 1f1ae93d8cd5140028e86d92483e349868b4f3f6) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-09-21opkg 0.1.8: remove it since it doesn't workRobert Yang
Remove opkg_0.1.8.bb and the related files since it doesn't work: - It doesn't support the "--force_postinstall" option which is used by package_ipk.bbclass. - It still doesn't work after remove the "--force_postinstall" option, it can't install the packages in complementary_pkgs.txt. [YOCTO #3136] (From OE-Core rev: 526da07578de2c6261d21bc339bca0d3b94d93cf) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-09-14opkg: Fix package dependency issue for preinstsRichard Purdie
When processing dependencies, we need to look for both the SW_INSTALL and SW_UNKNOWN states. If we don't do this, dependencies can be missed and preinst scripts can run before dependencies are all installed. This leads to package installation errors for packages like dbus-1 and associated user permission errors. (From OE-Core rev: 119ef2789484222b94559675a09adc399f3b6bf0) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-09-02nativesdk: Switch to using nativesdk as a prefix, not a suffixRichard Purdie
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. (From OE-Core rev: 81813c0e322dc04ce4b069117188d8a54dfddb8c) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-07-17Update proto -> protocol for recipesSaul Wold
(From OE-Core rev: 247fbed5a93800c44dc36e403f13bdc8dd704553) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-07-10opkg: fix installation of dev / dbg packagesPaul Eggleton
OE-Core revision ffe93e2a099e4cadb1829dc12a58a6d7bef9a5a7 moved opkg's configuration file into /etc/opkg, and opkg always reads all files under this directory even if -f is specified (as it is during do_rootfs in order to specify our own generated config file), and this means that after opkg-collateral is installed into the rootfs, this version of the config is used, resulting in opkg ignoring the list of packages it has already downloaded (since it now sees list_dir as /var/lib/opkg instead of the default /var/lib/opkg/lists) and thus it fails to install any of the "attemptonly" packages (including *-dev, *-dbg, etc.). If we change the -f option to ignore configuration files in /etc/opkg then we no longer have this problem. Fixes [YOCTO #2595]. (From OE-Core rev: 37df134557802ba116f001597b7cd5e9bc39e188) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-06-15opkg 0.1.8: do_fetch failed since no checksum specifiedRobert Yang
* We use meta/recipes-devtools/opkg/opkg_svn.bb by default, the opkg_0.1.8.bb failed since no checksum specified. * The add_vercmp.patch in both opkg/ and opkg-0.1.8/, remove the one in opkg-0.1.8/ This patch doesn't impact the output, so I think that we don't have to increment the PR. [YOCTO #2498] (From OE-Core rev: 316fac638646a50149f36ec4687b5a2a6d2e83b1) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-05-30opkg: use new update-alternativesMark Hatle
(From OE-Core rev: fc9c2fd512e592806b10d0273ca490c90072ff3f) Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-05-25opkg-nogpg: add file pathPaul Eggleton
There was no explicit path in FILESPATH for this recipe to allow it to find files referred to in SRC_URI (files shared with the standard opkg recipe). This problem may have been masked by the fetcher behaviour of looking for files last in DL_DIR, thus if opkg has been fetched beforehand there would have been no error. (From OE-Core rev: 0ddf7861d36452c0fe40b4ce439a2954de507965) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-05-01opkg-collateral: import fixes from OE-ClassicAndreas Oberritter
* Set lists_dir to /var/lib/opkg commit 16808bc4817492beba512f4e73bce8c232d1eafa Author: Marcin Juszkiewicz <hrw@openembedded.org> Date: Mon Mar 17 23:40:48 2008 +0000 * Update new options sample and move the opkg.conf to correct place commit cc9825d97962287df75e164aec456901292e1b7f Author: Tick Chen <ticktock35@gmail.com> Date: Mon Dec 29 19:41:47 2008 +0800 (From OE-Core rev: ffe93e2a099e4cadb1829dc12a58a6d7bef9a5a7) Signed-off-by: Andreas Oberritter <obi@opendreambox.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-04-16opkg-config-base/poky-feed-config-opkg: Always use ↵Richard Purdie
ALL_MULTILIB_PACKAGE_ARCHS to build arch list We need consistent configuration files for opkg so we might as well always use the full list. This is equal to PACKAGE_ARCHS in the non-multilib case. This fixes various multilib failures with ipk multilibs. (From OE-Core rev: bc85abc5013d0c831cc3c3823df45536c293aaba) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-04-10opkg: Add the condition for the content of arch.conf when enable multilibXiaofeng Yan
After successfully installed some lib32 multilib packages into the x86-64 image, we just found that the file content of /var/lib/opkg/status in rootfs changed after the very 1st boot, many lib32 related packages information are missing in that file. The missing arch "x86" in arch.conf cause the above problem. Adding the condition for the content of arch.conf when enable multilib. If build multilib image, "ALL_MULTILIB_PACKAGE_ARCHS" will be used instead of "PACKAGE_ARCHS". [YOCTO #1522] (From OE-Core rev: 700fc9a5d25ebb1f85cb9db11e41ba502744fe7e) Signed-off-by: Xiaofeng Yan <xiaofeng.yan@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit 1.2.3-korg (git 2.39.0) at 2024-05-04 01:39:07 +0000