On Sat, Sep 17, 2016 at 2:54 AM, Imants Cekusins
currently both config content (let's call it a *model*) and representation (*view*: specific config file type) are bundled.
if a common *model *is agreed on*,* package tool and IDE devs could pick any *view (*format*)* that best suits their / users needs.
such fragmentation would not break the workflow. If someone thinks of a convenient format and believe it worth their time to write a *controller* for it, why not?
Do I have to obtain whatever whizzy new controller you've come up with in order to work with your packages? Do I have to do this when everyone has come up with their own whizzy new controller and I need to fit their packages into whatever I am trying to write? -- brandon s allbery kf8nh sine nomine associates allbery.b@gmail.com ballbery@sinenomine.net unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net