libubox: new package
PATCH v4 1/2 libubox: new package
---
Changes:
v4: remove unneeded pkg-config macros
v3: add Lua support
v2: make package description more informative and fix license information
package/Config.in | 1 + package/libubox/Config.in | 7 +++++++ package/libubox/libubox.mk | 18 ++++++++++++++++++ 3 files changed, 26 insertions(+) create mode 100644 package/libubox/Config.in create mode 100644 package/libubox/libubox.mk
package/Config.in +1 -0
@@ -784,6 +784,7 @@ source "package/libsigc/Config.in" source "package/libsigsegv/Config.in" source "package/libtasn1/Config.in" source "package/libtpl/Config.in" +source "package/libubox/Config.in" source "package/libunwind/Config.in" source "package/liburcu/Config.in" source "package/linux-pam/Config.in"
package/libubox/Config.in new file +7 -0
@@ -0,0 +1,7 @@ +config BR2_PACKAGE_LIBUBOX + bool "libubox" + help + Small utility library for OpenWrt. It is a dependency of + libuci, that manages configuration files infrastructure. + + http://nbd.name/gitweb.cgi?p=luci2/libubox.git;a=summary
package/libubox/libubox.mk new file +18 -0
@@ -0,0 +1,18 @@ +################################################################################ +# +# libubox +# +################################################################################ + +LIBUBOX_VERSION = bbd846ec2d72b2629758b69dc122ac0b0f2c3e4b +LIBUBOX_SITE = git://nbd.name/luci2/libubox.git +LIBUBOX_LICENSE = LGPLv2.1, GPLv2, BSD-3c, MIT +LIBUBOX_INSTALL_STAGING = YES + +ifeq ($(BR2_PACKAGE_LUA),y) + LIBUBOX_DEPENDENCIES = lua +else + LIBUBOX_CONF_OPT = -DBUILD_LUA:BOOL=OFF +endif + +$(eval $(cmake-package))
Signature · 1 line
1.8.3.2
PATCH v4 2/2 libuci: new package
---
v4: remove unneeded pkg-config macros
v3: add Lua support
package/Config.in | 1 + package/libuci/Config.in | 9 +++++++++ package/libuci/libuci.mk | 19 +++++++++++++++++++ 3 files changed, 29 insertions(+) create mode 100644 package/libuci/Config.in create mode 100644 package/libuci/libuci.mk
package/Config.in +1 -0
@@ -785,6 +785,7 @@ source "package/libsigsegv/Config.in" source "package/libtasn1/Config.in" source "package/libtpl/Config.in" source "package/libubox/Config.in" +source "package/libuci/Config.in" source "package/libunwind/Config.in" source "package/liburcu/Config.in" source "package/linux-pam/Config.in"
package/libuci/Config.in new file +9 -0
@@ -0,0 +1,9 @@ +config BR2_PACKAGE_LIBUCI + bool "libuci" + select BR2_PACKAGE_LIBUBOX + help + libuci is intended to centralize the whole configuration + of a device running OpenWrt. This package will also install + CLI tool uci. + + http://wiki.openwrt.org/doc/techref/uci
package/libuci/libuci.mk new file +19 -0
@@ -0,0 +1,19 @@ +################################################################################ +# +# libuci +# +################################################################################ + +LIBUCI_VERSION = 262fede3e8c8c08c1eb0d1be9bf102232fb86cb9 +LIBUCI_SITE = git://nbd.name/uci.git +LIBUCI_LICENSE = LGPLv2.1 +LIBUCI_INSTALL_STAGING = YES +LIBUCI_DEPENDENCIES = libubox + +ifeq ($(BR2_PACKAGE_LUA),y) + LIBUCI_DEPENDENCIES += lua +else + LIBUCI_CONF_OPT = -DBUILD_LUA:BOOL=OFF +endif + +$(eval $(cmake-package))
Signature · 1 line
1.8.3.2
PATCH v4 2/2 libuci: new package
Dear Yegor Yefremov,
package/libuci/Config.in line 6
Quoted 6 lines · Yegor Yefremov
package/libuci/Config.in new file +6
-0+config BR2_PACKAGE_LIBUCI + bool "libuci" + select BR2_PACKAGE_LIBUBOX + help + libuci is intended to centralize the whole configuration + of a device running OpenWrt. This package will also install
What is a "device running OpenWrt" in the context of Buildroot ?
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com
PATCH v4 2/2 libuci: new package
Quoted 11 lines · Thomas Petazzoni
Dear Yegor Yefremov,
package/libuci/Config.in line 6
Quoted 6 lines · Yegor Yefremov
package/libuci/Config.in new file +6
-0+config BR2_PACKAGE_LIBUCI + bool "libuci" + select BR2_PACKAGE_LIBUBOX + help + libuci is intended to centralize the whole configuration + of a device running OpenWrt. This package will also install
Quoted 7 lines
What is a "device running OpenWrt" in the context of Buildroot ?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
libuci provides just another config infrastructure. All config files will be placed to /etc/config and you can read/write it's content via libuci or UCI CLI. OpenWrt is using this approach and also develops these packages. But it's usage is not limited to OpenWrt and can be used by any distribution. See http://wiki.openwrt.org/doc/uci for more details. I have found this tutorial for Ubunut:
http://www.wakoond.hu/2013/06/using-uci-on-ubuntu.html
I need these packages, because I have some programs I've developed for OpenWrt, but would also like to use in BR. Another usage were to play with swconfig (https://github.com/ringlej/swconfig). Of course you can compile swconfig without uci support, but uci like config is much more readable and handy: http://wiki.openwrt.org/doc/uci/network/switch.
And the real master plan were to port LuCI
(http://luci.subsignal.org/trac) or LuCI2 to BR, so that BR can get a "standard" web-frontend.
I think OpenWrt is good tag for those familiar with this infrastructure.
Yegor
PATCH v4 2/2 libuci: new package
Dear Yegor Yefremov,
Quoted 29 lines · Yegor Yefremov
Quoted 7 lines
package/libuci/Config.in line 6
Quoted 6 lines
package/libuci/Config.in new file +6
-0+config BR2_PACKAGE_LIBUCI + bool "libuci" + select BR2_PACKAGE_LIBUBOX + help + libuci is intended to centralize the whole configuration + of a device running OpenWrt. This package will also installQuoted 7 lines
What is a "device running OpenWrt" in the context of Buildroot ?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.comlibuci provides just another config infrastructure. All config files will be placed to
/etc/configand you can read/write it's content via libuci or UCI CLI. OpenWrt is using this approach and also develops these packages. But it's usage is not limited to OpenWrt and can be used by any distribution. See http://wiki.openwrt.org/doc/uci for more details. I have found this tutorial for Ubunut:
http://www.wakoond.hu/2013/06/using-uci-on-ubuntu.htmlI need these packages, because I have some programs I've developed for OpenWrt, but would also like to use in BR. Another usage were to play with swconfig (https://github.com/ringlej/swconfig). Of course you can compile swconfig without uci support, but uci like config is much more readable and handy: http://wiki.openwrt.org/doc/uci/network/switch.
Quoted 5 lines
And the real master plan were to port LuCI
(http://luci.subsignal.org/trac) or LuCI2 to BR, so that BR can get a "standard" web-frontend.I think OpenWrt is good tag for those familiar with this infrastructure.
Thanks for the explanation, but in fact I kind of knew all of this already. My message was more that your Config.in help text is misleading, as it doesn't really explain what libuci is, and it only indicates that it is "for OpenWrt", which doesn't make sense in the context of Buildroot. So I would rephrase the help text by indicating something like: "This library originates from the OpenWrt project to handle the configuration blablabla, but can also be used for the same purposes in projects other than OpenWrt".
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com
PATCH v4 2/2 libuci: new package
Quoted 39 lines · Thomas Petazzoni
Dear Yegor Yefremov,
Quoted 29 lines · Yegor Yefremov
Quoted 7 lines
package/libuci/Config.in line 6
Quoted 6 lines
package/libuci/Config.in new file +6
-0+config BR2_PACKAGE_LIBUCI + bool "libuci" + select BR2_PACKAGE_LIBUBOX + help + libuci is intended to centralize the whole configuration + of a device running OpenWrt. This package will also installQuoted 7 lines
What is a "device running OpenWrt" in the context of Buildroot ?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.comlibuci provides just another config infrastructure. All config files will be placed to
/etc/configand you can read/write it's content via libuci or UCI CLI. OpenWrt is using this approach and also develops these packages. But it's usage is not limited to OpenWrt and can be used by any distribution. See http://wiki.openwrt.org/doc/uci for more details. I have found this tutorial for Ubunut:
http://www.wakoond.hu/2013/06/using-uci-on-ubuntu.htmlI need these packages, because I have some programs I've developed for OpenWrt, but would also like to use in BR. Another usage were to play with swconfig (https://github.com/ringlej/swconfig). Of course you can compile swconfig without uci support, but uci like config is much more readable and handy: http://wiki.openwrt.org/doc/uci/network/switch.
Quoted 5 lines
And the real master plan were to port LuCI
(http://luci.subsignal.org/trac) or LuCI2 to BR, so that BR can get a "standard" web-frontend.I think OpenWrt is good tag for those familiar with this infrastructure.
Quoted 8 lines
Thanks for the explanation, but in fact I kind of knew all of this already. My message was more that your Config.in help text is misleading, as it doesn't really explain what libuci is, and it only indicates that it is "for OpenWrt", which doesn't make sense in the context of Buildroot. So I would rephrase the help text by indicating something like: "This library originates from the OpenWrt project to handle the configuration blablabla, but can also be used for the same purposes in projects other than OpenWrt".
O.K. Thomas. I'll resend the patches with proper description.
Yegor