Hi,

ACK on the patch. I was thinking about whether it makes sense to move out
the hardcoded package "busybox" -> "/bin/busybox" path facts into some kind
of external pkgname => multicall-executable-path mapping configuration but
there's probably not that many other relevant packages where this would apply.

Still I'd like to see the code somewhat generalized... rename the
"pkg_alternatives_check_busybox()" procedure to something like 
"pkg_alternatives_find_fallback()" and have it iterate an array of
"struct { char *pkgname; char *multicallpath; }" which may initially contain
just { { "busybox", "/bin/busybox" }, }.


Regards,
Jo

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Reply via email to