On Wed, 2016-02-24 at 14:17 -0500, Andrew Stitcher wrote: > On Tue, 2016-02-23 at 07:49 -0800, Justin Ross wrote: > > How will you avoid overwriting user config if you write to > > /etc? You'll > > need some sort of alternate extension, such as qdrouterd.conf.new. > > > > I'll note that this discussion is pretty much the exact discussion we > already had when arguing about where to install python, ruby etc. > binding libraries: > > There is a system installation of something, and it (in general) is > not > looking for its modules (config files) in the installation prefix of > proton, unless /usr is the installation prefix (which is not common > unless you are building system packages)
Nope, not the same. The SASL config file is an *application* config file. It belongs to qdrouterd. The SASL docs are clear that /etc/sasl2/app.conf is an acceptable default location but that applications can put it anywhere they want. Putting a qdrouterd config file in the qdrouterd's install prefix (of course using the default sasl path) *by default* seems like a sensible thing to do and allows us to install a *working* dispatch configuration out of the box and to not explode if you have say RPM and source installs on the same box. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
