On Wed, 2008-05-14 at 14:13 -0400, Scott Lawrence wrote:
> Now would be a great time to fix it.
>
> Take a look at the mechanism I added to
> sipXcommserverLib/include/sipXecs/SipXecsService substitutions in other
> components by making the paths available at run time (and they are easy
> to override in unit tests).
>
> > But back to the immediate problem -- Should I create yet another SIPX_*
> > symbol for the "sipxpresence" directory? It does seem a better location
> > than the "sipdb" directory.
>
> I'd say create on that maps to /var/sipxdata (or, more correctly in
> autoconf terms ${datadir}/sipxdata ), and then convert the others to use
> that as a base too.
Let me outline a plan:
Let us agree that all the directories that are now put
under /var/sipxdata by default will always be put under /var/sipxdata,
that is SIPX_VARDIR. I think we can make an exception for SIPX_TMPDIR,
as that's documented in the Filesystem Conventions, and I think that
many packages configure their temporary directories independently.
Then let us eliminate all the various SIPX_* symbols for subordinate
directories. I think they should even be removed from outputs of the
SipXecsService::Path routine, as I don't think that all references to
those directories have been made configurable -- all users of
subordinate directories should be able to assume the subordinate
directory names are fixed.
Opinions?
Dale
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
