John Crispin - 11:14 25.02.16 wrote: > > > On 25/02/2016 11:13, Michal Hrusecky wrote: > > Felix Fietkau - 10:22 25.02.16 wrote: > >> On 2016-02-25 10:05, Michal Hrusecky wrote: > >>> Opkg now uses sha256 by default and expects them. Making it understand > >>> md5s also > >>> and detect md5 sum so we can migrate from configuration that used md5. > >>> > >>> Signed-off-by: Michal Hrusecky <michal.hruse...@nic.cz> > >> OpenWrt itself does not support incremental upgrades of the system via > >> opkg, so we're not going to re-enable md5 support by default again. > >> > >> Can't you simply update your package lists to include both md5sum and > >> sha256, making this patch unnecessary? > > > > Not really, because I'm doing incremental update :-) > > > >> If not, you could submit a patch that makes md5 support optional (and > >> disabled by default). > > > > In patch it is optional and just uses md5 if hash found is not long enough > > to > > be sha providing backward functionality without changing default behaviour. > > And > > it is conditional. So I'll just disable it by default and that should take > > of > > it. Anything else before I resubmit? > > enabling md5 should be a compile time option. i do not want md5 support > compiled into opkg by default. >
Ok, will try to figure out how menus and config work and will put it behind config. _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel