David,
I do not disagree, and in fact I was not proposing a new configuration format.
What I tried to point out was
a) maintaining a 'meta-configuration' for some config overlay very quickly
becomes
very challenging and resource consuming
b) if the format has to be changed, in OpenWRT JSON
changing the format doesn't solve the problem, it just causes churn in all the
software.
The problem is the lack of standardization and the fact that the way things are
configured changes over time. Not everything is configured in UCI (and this will
always be the case because it's not worth
One other thought. If there is a desire to change the format, let's pick a
format that's already in use for configuring system rather than inventing yet
another one. We should survey the tools that are being written for managing
software defined datacenters (openstack and similar) and see if we
Hello Matthias,
can't provide qualified feedback to your proposal, but at least want to post my
experience and hope that it is valuable for the discussion.
Our company develops highly specialized WLAN products for decades, for a long
time
based on OpenWRT. The niche market we are in has a
On 03/05/2015 08:25 PM, David Lang wrote:
On Thu, 05 Mar 2015 13:36:10 +0100, Matthias Schiffer wrote:
Hi,
during the development of our Freifunk firmware framework Gluon we've
come to the conclusion that the current UCI configuration format using
static files doesn't always fit our needs.
On Thu, 05 Mar 2015 13:36:10 +0100, Matthias Schiffer wrote:
Hi,
during the development of our Freifunk firmware framework Gluon
we've
come to the conclusion that the current UCI configuration format
using
static files doesn't always fit our needs. Therefore we propose a new
feature we've
You even make the conflicts reliably handled by processing the contents of,
say, /etc/config/wireless.d/* in sort order (the old 01-blah, 02-foo
trick). This way, if one package drops in a config file that you want to
override, you only have to make sure that your override comes after the file
Hi,
during the development of our Freifunk firmware framework Gluon we've
come to the conclusion that the current UCI configuration format using
static files doesn't always fit our needs. Therefore we propose a new
feature we've called UCI overlays.
The basic idea is that we'd like to provide UCI
