Currently leds migration scripts in ar71xx and lantiq share a lot of
logic and introducing leds migration to another target would mean
copying this code, again. Therefore add common logic to library in
base-files package.
Suggested-by: Petr Štetiar <yn...@true.cz>
Signed-off-by: Petr Štetiar <yn...@true.cz>
Signed-off-by: Tomasz Maciej Nowak <tome...@o2.pl>
---
Changes in v2 to:
"base-files: add leds migration"
As OpenWrt is close to branch new stable version I removed and postponed
the ar71xx and lantiq target migration to not introduce new bugs.
.../files/lib/functions/migrations.sh | 39 +++++++++++++++++++
1 file changed, 39 insertions(+)
create mode 100644 package/base-files/files/lib/functions/migrations.sh
diff --git a/package/base-files/files/lib/functions/migrations.sh
b/package/base-files/files/lib/functions/migrations.sh
new file mode 100644
index 0000000000..b180a0242f
--- /dev/null
+++ b/package/base-files/files/lib/functions/migrations.sh
@@ -0,0 +1,39 @@
+#!/bin/sh
+
+. /lib/functions.sh
+
+migrate_led_sysfs() {
+ local cfg="$1"; shift
+ local tuples="$@"
+ local sysfs
+ local name
+
+ config_get sysfs ${cfg} sysfs
+ config_get name ${cfg} name
+
+ [ -z "${sysfs}" ] && return
+
+ for tuple in ${tuples}; do
+ local old=${tuple%=*}
+ local new=${tuple#*=}
+ local new_sysfs
+
+ new_sysfs=$(echo ${sysfs} | sed "s/${old}/${new}/")
+
+ [ "${new_sysfs}" = "${sysfs}" ] && continue
+
+ uci set system.${cfg}.sysfs="${new_sysfs}"
+
+ logger -t led-migration "sysfs option of LED \"${name}\"
updated to ${new_sysfs}"
+ done;
+}
+
+migrate_leds() {
+ config_load system
+ config_foreach migrate_led_sysfs led "$@"
+}
+
+migrations_apply() {
+ local realm="$1"
+ [ -n "$(uci changes ${realm})" ] && uci -q commit ${realm}
+}
--
2.21.0
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
