#16837: configuration should be more task oriented and less "package" oriented
-------------------------+-------------------------------------
Reporter: brian@… | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone: Barrier Breaker (trunk)
Component: base system | Version: Trunk
Keywords: |
-------------------------+-------------------------------------
Much of the current configuration is geared towards configuring particular
packages, like dnsmasq. But this then means that if one day dnsmasq is
replaced by something else, the previous configuration needs to be
migrated to the "package configuration" for the new package.
In general, configuration should be implementation (i.e. which package
implements the configuration) agnostic and more generic task oriented.
So to continue with the dnsmasq example, the configuration system should
have generic settings which (could) represent dnsmasq configuration but
the configuration system takes care of converting those generic settings
into dnsmasq settings. Then if one day dnsmasq is replaced, it's only
that translation (which is all code) that needs to change, not users'
actual configurations.
This also alleviates the user's need to understand how given packages are
configured and gives them a more generic task oriented configuration which
most people grasp without having to familiarize themselves with a piece of
software, or even understand that it's the configuration for such a piece
of software that achieves their goals.
Indeed, Luci seems to have this level of abstraction, but IMHO, even
/etc/config/* should abstract that away.
--
Ticket URL: <https://dev.openwrt.org/ticket/16837>
OpenWrt <http://openwrt.org>
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
[email protected]
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-tickets
