aboutsummaryrefslogtreecommitdiffstats
path: root/meta/recipes-devtools/opkg/opkg
AgeCommit message (Collapse)Author
2015-02-03opkg: Backport improvements to opkg-keyPaul Barker
The improvements to opkg-key made for v0.3.0 are backported. The rest of v0.3.0 needs further testing and bugfixing prior to release, but the improvements to opkg-key have been tested and work well. Signed-off-by: Paul Barker <paul@paulbarker.me.uk>
2015-02-03opkg: Merge in opkg-collateralPaul Barker
All non-arch-specific and non-distro-specific configuration is now kept in the main 'opkg' recipe and package. Signed-off-by: Paul Barker <paul@paulbarker.me.uk>
2015-01-23opkg: fix libtoolize errorRobert Yang
Fixed: libtoolize: error: AC_CONFIG_MACRO_DIRS([m4]) conflicts with ACLOCAL_AMFLAGS=-I shave. They are already included by configure.ac: AC_CONFIG_MACRO_DIR([m4]) AC_CONFIG_MACRO_DIR([shave]) Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
2014-11-25opkg: Update patch statusPaul Barker
Both patches against opkg have been accepted upstream with modifications and will be included in the v0.3.0 release. Signed-off-by: Paul Barker <paul@paulbarker.me.uk> Signed-off-by: Ross Burton <ross.burton@intel.com>
2014-11-25opkg: Upgrade to v0.2.4Paul Barker
The patches for opkg have been rebased using git so that they apply cleanly onto the new release. Signed-off-by: Paul Barker <paul@paulbarker.me.uk> Signed-off-by: Ross Burton <ross.burton@intel.com>
2014-11-04opkg: fix remove pkg with --force-removal-of-dependent-packages failedHongxu Jia
opkg remove perl --force-removal-of-dependent-packages ... Removing package perl-module-extutils-mm-dos from root... ... Removing package perl-module-extutils-mm-dos from root... You can force removal of packages with failed prerm scripts with the option: --force-remove No packages removed. Collected errors: * pkg_run_script: Internal error: perl-module-extutils-mm-dos has a NULL tmp_unpack_dir. * opkg_remove_pkg: not removing package "perl-module-extutils-mm-dos", prerm script failed ... While remove pkg with '--force-removal-of-dependent-packages', pkg may be added to remove list multiple times, add status check to make sure pkg only be removed once. [YOCTO #6819] Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2014-08-15opkg: Protect add-exclude.patch from malloc failurePaul Barker
In the code added by add-exclude.patch, the return values of malloc and realloc were not checked before being dereferenced. In opkg we can use xmalloc and xrealloc instead of malloc and realloc. These functions terminate the program instead of returning NULL if memory allocation fails. Signed-off-by: Paul Barker <paul@paulbarker.me.uk> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-04-25opkg: Upgrade to v0.2.2Paul Barker
The patches for opkg have been rebased using git so that they apply cleanly onto the new release. Signed-off-by: Paul Barker <paul@paulbarker.me.uk> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-02-20opkg: Fix add-exclude.patchPaul Barker
The case statement for ARGS_OPT_ADD_EXCLUDE added to the argument handling switch statement in opkg was missing a "break;" at the end, so it was falling through into the handler for ARGS_OPT_NOACTION. Thus when "--add-exclude" was specified on the command line it was as if "--noaction" was also being specified. This appears to be the root cause of YP bug 5311. Tested using the case described by Alexandru Georgescu in YP bug 5311: MACHINE ??= "qemux86" IMAGE_INSTALL_append = " man" PACKAGE_EXCLUDE = "man" PACKAGE_CLASSES ?= "package_ipk" Built image and boot tested on qemu, ensured that man was not installed but the rest of the system was installed correctly. Signed-off-by: Paul Barker <paul@paulbarker.me.uk> Cc: Mark Hatle <mark.hatle@windriver.com> Cc: Saul Wold <saul.wold@intel.com> Cc: Alexandru Georgescu <alexandru.c.georgescu@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
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. 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. 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
Signed-off-by: Jonathan Liu <net147@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
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. Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
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. Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
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) Signed-off-by: Paul Barker <paul@paulbarker.me.uk> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-08-01opkg: 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. Signed-off-by: Paul Barker <paul@paulbarker.me.uk> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-07-18Upstream-Status: Correct capitalizationSaul Wold
Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-06-17opkg: 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. Signed-off-by: Paul Barker <paul@paulbarker.me.uk> 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. Signed-off-by: Marko Lindqvist <cazfi74@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
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 Signed-off-by: Martin Jansa <Martin.Jansa@gmail.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. Signed-off-by: Enrico Scholz <enrico.scholz@sigma-chemnitz.de> 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. 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] 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. 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.) 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 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] Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
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 Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2012-09-21opkg: replace local patches with git patches submitted upstreamMartin Jansa
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
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. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Saul Wold <sgw@linux.intel.com>
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]. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-03-22Fix common typoes "existant", "dependant" and variationsRobert P. J. Day
Fix a couple common typoes, all contained within comments so there should be no effect on functionality. Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-12-22opkg: Fix installation order in feeds with mutiple providers of packagesRichard Purdie
If two packages were available of differing priority, this would confuse opkg and it was ignoring the dependency in the new dependency ordering code. This changes it not to ignore these cases by setting the badly named 'quiet' parameter accordingly. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-12-19opkg: Drop the offlineroot_varname patchRichard Purdie
This break things for on target opkg usage since $D must remain unset there. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-12-19opkg: Add logic to detect and creak circular dependenciesRichard Purdie
This addresses some of the concerns about the previous opkg changes allowing it to break out of circular dependency loops with just a notice in the logs rather than effectively going OOM. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-12-16opkg: Update svn 625 -> 633 and fix preinst issuesRichard Purdie
There is a major issue with opkg images at the moment as preinst functions are not being executed before their dependencies are installed and this is leading to corruption of images containing avahi/dbus in particular. There are various changes in upstream opkg in the last 8 revisions which make changes in this area but sadly these aren't enough to get things working for us. I've updated to the latest svn revision with this patch since it makes sense to pull in those changes first and then supplement them with the attached patches. There is a full description of the patches in the patch headers but in summary they: a) Ensure preinst functions execute with their dependencies installed. This is a pretty invasive change as it changes the package install ordering in general. b) Ensure opkg sets $D, not $PKG_ROOT which we don't use c) Change opkg to allow execution of postinstall functions which fail resulting in execution on the target device as rootfs_ipk.bbclass currently does manually. The remaining changes interface this with the rest of the OE build infrastructure, adding in the option to tell opkg to run the preinst and postinst functions, ensure the correct environment is present for the postinst scripts and removing the now unneeded rootfs_ipk class code which opkg now does itself. [YOCTO #1711] Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-11-14opkg: Ensure we use the uname/gname fields when extracting tarballsRichard Purdie
When extracting packages onto the target system in particular, we really want to ensure the name fields in the tarball are used over and above the numerical uid/gid values. This patch adds this functionality to opkg and ensures package upgrades work correctly permission wise. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-05-23opkg_svn.bb: Install rcS.d into $D instead of $IMAGE_ROOTFSKhem Raj
Remove headerfix.patch, its already applied upstream Signed-off-by: Khem Raj <raj.khem@gmail.com>
2011-05-12recipes: add Upstream-Status for multiple recipesDongxiao Xu
hostap: add upstream status for hostap-fw-load.patch lrzsz: add upstream status for lrzsz's patches bluez: add upstream status for bluez's patches bluez-dtl1-workaround: add upstream status for COPYING.patch libgsmd: add upstream status for gsm's patches. gypsy: add upstream status for gypsy's patch libpcap: add upstream status for libpcap's patches ppp: add upstream status for ppp's patches libtelepathy: add upstream status for libtelepathy's patches telepathy-python: add upstream status for telepahty-python's patches wireless-tools: add upstream status for wireless-tools's patches wpa-supplicant: add upstream status for wpa-supplicant zeroconf: add upstream status for zeroconf's patch glibc: add upstream status for glibc's patches dpkg: add upstream status for dpkg's patches makedevs: add upstream status for makedevs's patch opkg: add upstream status for opkg's patches opkg-utils: add upstream status for opkg-utils's patch minicom: add upstream status for minicom patches rpcbind: add upstream status for rpcbind's patch which: add upstream status for which's patch clutter-gst: add upstream status for clutter-gst's patches flac: add upstream status for flac's patches gst-ffmpeg: add upstream status for gst-ffmpeg's patch liba52: add upstream status for liba52's patch libid3tag: add upstream status for libid3tag libmusicbrainz: add upstream status for libmusicbrainz's patch pulseaudio: add upstream status for pulseaudio patches db: add upstream status for db's patch neon: add upstream status for neon's patch taglib: add upstream status for taglib's patches libetpan: add upstream status for libetpan's patch libopensync: add upstream status for libopensync's patches libopensync-plugin-evolution2: add upstream status for its patch libopensync-plugin-syncml: add upstream status for its patch libsyncml: add upstream status for libsyncml's patch empathy: add upstream status for empathy's patch wv: add upstream status for wv's patch xournal: add upstream status for xournal's patch Signed-off-by: Dongxiao Xu <dongxiao.xu@intel.com>
2011-02-01opkg: Update to svn r596 to fix segfault when upgrading packagesKoen Kooi
The longlinks patch is upstream and and be removed now Signed-off-by: Koen Kooi <koen@dominion.thruhere.net> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2010-12-22opkg: Update to svn r590 to fix symbolic link issuesRichard Purdie
See the longlinksfix patch for details but symlinks over 100 chars long were broken in sdk tarballs and its due to problems in the inbuilt tar in libbb in opkg. The patch fixes this and switched to svn r590 which already had partial fixes. Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-08-27Major layout change to the packages directoryRichard Purdie
Having one monolithic packages directory makes it hard to find things and is generally overwhelming. This commit splits it into several logical sections roughly based on function, recipes.txt gives more information about the classifications used. The opportunity is also used to switch from "packages" to "recipes" as used in OpenEmbedded as the term "packages" can be confusing to people and has many different meanings. Not all recipes have been classified yet, this is just a first pass at separating things out. Some packages are moved to meta-extras as they're no longer actively used or maintained. Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>