Thanks for all the feedback! I made changes based on all the feedback from the last series of opkg integration patches. I found and fixed a few other problems as well. Everything is working quite nicely now.
[PATCH 01/13] Added install_config [PATCH 02/13] temporary ipkg.conf doesn't need a real source [PATCH 03/13] opkg: Added option to install config [PATCH 04/13] build images from ipkg repository [PATCH 05/13] host-opkg: Added new host package. [PATCH 06/13] host-opkg-utils: Added new host package. [PATCH 07/13] make ptxd_make_xpkg more generic [PATCH 08/13] opkg can now be used instead of ipkg [PATCH 09/13] opkg: patch up to SVN trunk [PATCH 10/13] opkg: don't symlink /tmp to /usr/lib/opkg [PATCH 11/13] host-openssl: added for ipkg-repository signing [PATCH 12/13] Added option to sign ipkg-repository [PATCH 13/13] opkg: make signature checking work on target I've included the description from last time again: Opkg is a replacement for the no longer maintained ipkg. This series of patches allows opkg to be used instead of ipkg for the creation of packages and image files. Ipkg is still used by default but opkg can be used instead by changing “Host Tools/package management” from ipkg to opkg within ptxdist menuconfig. Following the example of other embedded distros such as Angstrom and openwrt the .ipk filename extension has been retained. My intent is to introduce opkg in a non-intrusive manner, however since ipkg is no longer maintained I'd suggest support for it eventually be phased out in favor of opkg. To facilitate the use of package repositories in security sensitive environments an option is now available to sign the repository with openssl. Opkg supports verification of this signature. This allows the target to verify the authenticity of packages prior to installation. I've also added install_config which works identically to install_alternative with the exception that it marks the file as a configuration file in the .ipk file. I have yet to commit any .make files containing usage of install_config since it's use can change the behavior ipkg and opkg exhibit when upgrading packages on the target. We've been using a method of handling configuration files similar to this to conduct upgrades on live field devices with ptxdist 1.0 for several years. In our systems we've found it necessary in certain cases to include a post install script which selectively modifies the existing configuration file since neither leaving the existing configuration untouched nor replacing it are acceptable solutions. Regards, George McCollister -- ptxdist mailing list [email protected]
