Hi, We have a similar issue with luci-httpclient in that we need to enable ssh for our epoint-scada package to work. Without bumping the version number, we cannot have our packages installed on a binary OpenWrt distribution either.
Králik Barnabás wrote: > I have modified OpenSSL’s Config.in and Makefile and added an option in > the make menuconfig menu where OpenSSL threadedness can be enabled or > disabled; I made my pound package depend on this config option. Side note: Does it work well? The libc in OpenWrt sometimes has issues with threaded libraries which is why threading often gets turned off. > If I > download this package to my router (ar71xx, Netgear WNDR3700 btw) and > then say opkg install libopenssl1.0.0d-1_ar71xx.ipk, opkg says: > “opkg_install_pkg: Package libopenssl md5sum mismatch. Either the opkg > or the package index are corrupt. Try 'opkg update'.” If I modify > OpenSSL’s PKG_RELEASE to another value, everything works fine. > > I would like to ask what is the appropriate step to do in such a > situation. My idea would be to create a libopenssl-threads package that > is accepted by opkg as libopenssl too; unfortunately I don’t know how to > achieve that with the package Makefile; however this idea seems less > than elegant for me. What do you think? Adding the configuration option and making your package dependent on it is a step in the right direction. If you want your package to be compatible with the current binary distribution of OpenWrt, you need to bump the version number (PKG_RELEASE) just as you did. Otherwise, I would suggest that you start your own repository until OpenWrt decides to incorporate your patch (which you should submit first, of course) adding the configuration option. I do not think that you need a spearate libopenssl-threads package. Cheers, -- Daniel
signature.asc
Description: OpenPGP digital signature
_______________________________________________ openwrt-devel mailing list [email protected] https://lists.openwrt.org/mailman/listinfo/openwrt-devel
