[Buildroot] [PATCH v4 2/2] libuci: new package

[Yegor Yefremov]

On Thu, Mar 20, 2014 at 3:51 PM, Thomas Petazzoni
<thomas.petazzoni at free-electrons.com> wrote:
> Dear Yegor Yefremov,
>
> On Thu, 20 Mar 2014 09:17:55 +0100, Yegor Yefremov wrote:
>
>> >> +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
>> > --
>> > 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.
>
> 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