Don't missunderstand me please: I say switch to ports but don't break old configs by means of keeping port working in the background, maybe supported with a deprecation message for users with old config ;)
.. ede On 28.02.2010 13:40, Matthias Buecher / Germany wrote: > To me that's even more confusing. > Either use "port" or "ports", not both. > > Maddes > > On 28.02.2010 12:21, [email protected] wrote: >> Let's keep it simple and backward compatible. > >> Change new config to ports but also add old port setting to this list. >> Something like: > >> config_get ports "${section}" Ports >> config_get port "${section}" Port >> ports="$port $ports" > >> Perfect of course would be a log message telling deprecation of port >> setting in favor for ports. > >> .. ede > >> On 28.02.2010 11:58, Matthias Buecher / Germany wrote: >>> Just my two cents: >>> Maybe some OpenWrt team members can review if the option rename causes >>> hassle to the normal end user. >>> Multiple ports will be rarely used by normal users (same as with multiple >>> instances), and advanced users should find out fast that they can list >>> several ports separated by space in the port option. >>> On the other side the plural "ports" fits much better the new functionality. >>> >>> As I said just my two cents >>> Maddes >>> >>> On 28.02.2010 11:30, Stijn Tintel wrote: >>>> On 28-02-10 11:28, Stijn Tintel wrote: >>>>> This patch allows multiple listen ports to be configured for dropbear in >>>>> /etc/config/dropbear. It renames the 'Port' option to 'Ports', so this >>>>> will break existing configs. >>>>> >>>>> Regards, >>>>> Stijn >>>>> >>>> 2nd attempt with attach :-) > _______________________________________________ openwrt-devel mailing list [email protected] https://lists.openwrt.org/mailman/listinfo/openwrt-devel _______________________________________________ openwrt-devel mailing list [email protected] https://lists.openwrt.org/mailman/listinfo/openwrt-devel
