summaryrefslogtreecommitdiff
path: root/meta/recipes-devtools/opkg
AgeCommit message (Collapse)AuthorFiles
2015-12-22opkg: upgrade to v0.3.1Alejandro del Castillo9
* Drop merged patches * Add patch to fix crash when using the libsolv backend * Add patch to add pkgconfig support for libsolv * Add libsolv support via a PACKAGECONFIG option. Signed-off-by: Alejandro del Castillo <alejandro.delcastillo@ni.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2015-11-25opkg: add cache filename length fixesAlejandro del Castillo5
Signed-off-by: Alejandro del Castillo <alejandro.delcastillo@ni.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2015-09-29opkg: create opkg.lock in /run instead of /var/runJonathan Liu2
This avoids a "Could not unlink" warning when extracting a /var/run symbolic link pointing to /run from the base-files package as it is unable to unlink the /var/run directory when it contains opkg.lock. This also fixes an issue where /var/run is created as a directory instead of a symbolic link to /run. Signed-off-by: Jonathan Liu <net147@gmail.com> Acked-by: Anders Darander <anders@chargestorm.se> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-09-21opkg: Include stdio.h for FILE definitionKhem Raj2
Helps with compling it on musl Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2015-09-01opkg: upgrade to v0.3.0Alejandro del Castillo7
Changes required: - Rename opkg-cl to opkg - Add libarchive dependency - Drop backport patches - Drop obsolete directory options - Add patch to handle empty index files Based on initial work by Paul Barker. Signed-off-by: Alejandro del Castillo <alejandro.delcastillo@ni.com> CC: Paul Barker <paul@paulbarker.me.uk> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-08-01opkg: solve inconsistency of using different lists directoriesAlejandro Hernandez1
Default behavior of opkg was to use ${OPKGLIBDIR}/opkg/lists; but in our recipe we modify it to ${OPKGLIBDIR}/opkg/${OPKGLIBDIR}/opkg/, when appending package-management to IMAGE_FEATURES these lists are populated during build time (using the default directory), but since our config was different these populated lists were never used at runtime, this patch solves this inconsistency by using default behavior for both build time and runtime. [YOCTO #6966] Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-07-31opkg: read config file from ${sysconfdir} instead of /etcAndré Draszik1
Opkg's configure script doesn't use the value from --sysconfdir to determine the location of the conf file, it uses the value from --with-opkgetcdir Signed-off-by: Ross Burton <ross.burton@intel.com>
2015-07-16opkg-arch-config: set S correctlyRoss Burton1
This recipe doesn't unpack any source, so set S to ${WORKDIR}. Signed-off-by: Ross Burton <ross.burton@intel.com>
2015-07-12opkg: remove do_configure_prependRobert Yang1
There is no -Werror in libopkg/Makefile.am any more. Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-04-13opkg: remove libopkg-dev and libopkg-staticdev from PACKAGESRobert Yang1
There should be only one dev and dbg package Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-03-20opkg: drop already applied patchPaul Eggleton2
This patch was part of the 0.2.4 release. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
2015-03-09opkg: Fix error when recompiledGary Thomas1
If this package were ever recompiled, i.e. do_compile is rerun as a result of a compiler change, etc., the 'opkg.conf' file would be incorrectly updated, leading to an error: * opkg_conf_set_option: Duplicate option lists_dir, using first seen value "/var/lib/opkg". Signed-off-by: Gary Thomas <gary@mlbassoc.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2015-02-23recipes: Delete superfluous assignments, S = ${WORKDIR}/${BP}Robert P. J. Day1
Given that bitbake.conf sets the default values: BP = "${BPN}-${PV}" S = "${WORKDIR}/${BP}" there are a number of recipes that set the variable S completely superfluously, so get rid of them. Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-02-21opkg: fix systemd unit installationRoss Burton1
SYSTEMD_SERVICE doesn't need to be set conditionally, and units should be installed if the systemd DISTRO_FEATURE is enabled, not if sysvinit isn't enabled. Signed-off-by: Ross Burton <ross.burton@intel.com>
2015-02-03opkg-keyrings: New recipePaul Barker1
This recipe wraps package and package feed verification keys into a package, making the management and deployment of verification keys much easier. Comments on how to select keys for inclusion in this package are provided in the recipe file. Signed-off-by: Paul Barker <paul@paulbarker.me.uk>
2015-02-03opkg: Backport improvements to opkg-keyPaul Barker2
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 Barker3
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-02-03opkg: Merge opkg.inc into recipe and tidy upPaul Barker2
There is no benefit to having a separate .inc file when we only support one version of opkg. The .inc file had multiple do_install_append functions and several variables were defined out of the usual order. This arrangement should be better. Signed-off-by: Paul Barker <paul@paulbarker.me.uk>
2015-02-03opkg-collateral: Simplify source filesPaul Barker4
Instead of having the source files 'opkg.conf.comments', 'dest' and 'src', we simply have one 'opkg.conf' file containing all the necessary configuration. This does mean that replacing 'src' in a bbappend to define distro-specific package feeds is no longer supported, but these feed configurations should be packaged separately from the rest of the opkg configuration anyway so that things can be updated independently. The best recipe to use for managing feed configs is currently distro-feed-config in the meta-oe layer. Signed-off-by: Paul Barker <paul@paulbarker.me.uk>
2015-02-03opkg-arch-config: Renamed from opkg-config-basePaul Barker2
The name 'opkg-arch-config' is much more descriptive. Signed-off-by: Paul Barker <paul@paulbarker.me.uk>
2015-01-23meta: set proper S valuePetter Mabäcker1
After removal of auto-creating S we must ensure that all recipes are using a proper value for S. Fix all recipes that only need to set S equals to WORKDIR. [YOCTO #5627] Signed-off-by: Petter Mabäcker <petter@technux.se>
2015-01-23opkg: fix libtoolize errorRobert Yang2
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-12-24opkg-collateral: Use new lists_dir syntaxPaul Barker1
Since opkg v0.2.3, it has been possible to use the new syntax for the 'lists_dir' option in an opkg configuration file. From v0.3.0, this new syntax is required. The new syntax matches the way other options are set. Signed-off-by: Paul Barker <paul@paulbarker.me.uk> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-11-25opkg: Update patch statusPaul Barker2
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 Barker3
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 Jia2
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-23opkg: Add runtime dep on gnupg if 'gpg' is in PACAKGECONFIGPaul Barker1
The 'opkg-key' utility requires gpg to manage the list of trusted keys. The ability to verify package signatures is not much use without the ability to add keys to the trusted list... Signed-off-by: Paul Barker <paul@paulbarker.me.uk> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-08-15opkg: Protect add-exclude.patch from malloc failurePaul Barker1
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 Barker3
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-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-04-25Globally replace oe.utils.contains to bb.utils.containsOtavio Salvador1
BitBake has the exact same code as oe.utils.contains so there's no reason to duplicate it. We now rely on the bb.utils.contains code for metadata. Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-03-07opkg/dpkg: remove the postinstallsLaurentiu Palcu1
Just use the run-postinsts recipe for running first boot postinstalls. [YOCTO #5666] Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-02-20opkg: Upgrade to v0.2.1Paul Barker2
v0.2.1 of opkg is a minor bugfix release. Tested on qemux86 to ensure opkg-native can build an image and opkg can update, remove and install packages. Signed-off-by: Paul Barker <paul@paulbarker.me.uk> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2014-02-20opkg: Fix add-exclude.patchPaul Barker1
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>
2014-01-17opkg/opkg-utils/chkconfig: Clean up u-a-cworth referencesRichard Purdie1
Catch some u-a-cworth references that slipped through the move of u-a to opkg-utils and its rename to -opkg. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-01-16opkg: No longer PROVIDES update-alternativesPaul Barker1
The new provider is the opkg-utils recipe. Signed-off-by: Paul Barker <paul@paulbarker.me.uk> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-01-02Replace one-line DESCRIPTION with SUMMARYPaul Eggleton3
A lot of our recipes had short one-line DESCRIPTION values and no SUMMARY value set. In this case it's much better to just set SUMMARY since DESCRIPTION is defaulted from SUMMARY anyway and then the SUMMARY is at least useful. I also took the opportunity to fix up a lot of the new SUMMARY values, making them concisely explain the function of the recipe / package where possible. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
2013-12-05classes/recipes: More optimal DISTRO_FEATURES referencesRichard Purdie1
Using the contains function results in more optimal sstate checksums resulting in better cache reuse as we as more consistent code. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-11-22opkg: Don't use update-alternativesPaul Barker1
The symlink from 'opkg' to 'opkg-cl' doesn't need to be created with update-alternatives as there isn't any alternative. Instead it can be created by hand in do_install_append. Signed-off-by: Paul Barker <paul@paulbarker.me.uk> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-11-22opkg: Add PACKAGECONFIG optionsPaul Barker1
Instead of hardcoding EXTRA_OECONF to disable things, we add PACKAGECONFIG options for gpg, curl, ssl-curl, openssl, sha256 and pathfinder. By default all these options are disabled. Signed-off-by: Paul Barker <paul@paulbarker.me.uk> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-11-22opkg: Update to version 0.2.0Paul Barker3
Signed-off-by: Paul Barker <paul@paulbarker.me.uk> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-10-30systemd-compat-units: run-postinsts fix script linkAndreas Müller1
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. Signed-off-by: Andreas Müller <schnitzeltony@googlemail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-10-30opkg: putting the service files into PNRoy Li1
Signed-off-by: Roy Li <rongqing.li@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-10-04opkg: ignore result of opkg configureMuhammad Shakeel1
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 Shakeel3
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 Liu1
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 Hatle2
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 Hatle2
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-14opkg.inc: remove the obsolete POSTLOG variableChen Qi1
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. Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-08-13opkg: Fix possible installation of GPLv3 headerPaul Barker2
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>
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-25 13:05:10 +0000