On Tue, 2008-09-16 at 14:28 +0000, Scott Lawrence wrote:
> In the sipXconfig changes during 3.11 a large number of new files have
> been added under /etc/sipxpbx that are _not_ configuration files.  A
> configuration file is one that normal configuration may require changes
> to under the control of a user.  In particular, a template from which a
> configuration file is generated is not itself a configuration file: it's
> a data file, so it really belongs in %datadir
> (normally /usr/share/sipxecs/<some-path> )
> 
> Adding files to /etc/sipxpbx makes snapshots much larger and adds no
> value to them.  We've had an issue open on this for quite some time:
> 
>  http://track.sipfoundry.org/browse/XCF-2185
> 
> and the situation is getting worse rather than better.  If we don't fix
> this before 4.0, it will only make moving them later more difficult.
> Surely this is mostly a question of changing one path constant
> somewhere?
> 

Scott,
  I agree, though I am also one of the perpetrators.  All of the new
sipx service files were added in etc.  These should be moved.  There are
two primary things to change, as far as I know.  The first is where the
settings code looks for settings files and the second is where the
velocity code looks for templates.  One problem is that there are many
settings files and velocity templates, not just the ones added in the
past few months.  I will need to look and see if we can specify multiple
directories for this code to look for its files.  If so, we can do a
gradual migration.  If not, it is going to have to be all at once.
Also, plugins will be affected by this change.  Currently sipXconfig
plugins are placed in the etc dir.  After this change (if we do the
"everything needs to move" approach) plugins will need to be installed
differently.

Kevin


_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev

Reply via email to