Hi Ben!
> Since I don't have any bug to report... here some thoughts about the
> configuration files handling...
>
> I want to be able to use completely distinct paths for |FSVS_CONF| /
> |FSVS_WAA |based on the directory I'm in.
May I ask why? I see some reasons, but they are too low on my priority list.
> For example, here my different
> projects root directories and associated CONF / WAA paths :
>
> /home/project-a (|FSVS_CONF=|/usr/local/var/fsvs/project-a/conf ||
> |FSVS_WAA||=|/usr/local/var/fsvs/project-a/waa)
> /home/project-b (|FSVS_CONF=|/usr/local/var/fsvs/project-b/conf ||
> |FSVS_WAA||=|/usr/local/var/fsvs/project-b/waa)
> /home/project-c (|FSVS_CONF=|/usr/local/var/fsvs/project-c/conf ||
> |FSVS_WAA||=|/usr/local/var/fsvs/project-c/waa)
> ...
>
> I think that one possibility could be to add in the priority order
> "$PWD/.fsvs/config":
>
> * command line //(highest)
> * environment variables. These are named as |FSVS_/{uppercase option
> name}/|.
> * $PWD/.fsvs/config <================== NEW ONE !!!!
> * |$HOME/|.fsvs/wc-dir/Config
> * |$FSVS_CONF/wc-dir/Config|
> * |$HOME/|.fsvs/config
> * |$FSVS_CONF/config|
>
> if I understand right your config schema
> (http://fsvs.tigris.org/source/browse/*checkout*/fsvs/trunk/www/doxygen/html/group__options.html)
> ... I would have to have in ./.fsvs/config:
>
> conf=||/usr/local/var/fsvs/project-a/conf
> waa=||/usr/local/var/fsvs/project-a/waa
Sorry, these are not implemented. And if they'd be, they'd be called
waa_path amd conf_path.
> So, simply by cd'ing into the project's root directory (for example:
> /home/project-a), I would get the right configuration loaded
> (/home/project-a/.fsvs/config) and the right paths
> (|FSVS_CONF=|/usr/local/var/fsvs/project-a/conf ||
> |FSVS_WAA||=|/usr/local/var/fsvs/project-a/waa)...
>
> That would save me lot of time, since I have to change a lot between
> different projects and tracking configuration (or more exactly... not
> making error) is becoming rapidly a nightmare...
>
> Does it make sense?
Yes, of course.
I just committed a small change (that I needed myself) so that
$FSVS_CONF/<....>/config is read and parsed - so you can set options
depending on your WC.
Is that what you need?
If you really want to separate your FSVS_CONF and FSVS_WAA directories, a
switch in some shell script might be better suited.
1) I wouldn't like to "dirty" the WC with FSVS' files
2) What happens if you're not in $WC (with .fsvs/config in it), but in
$WC/subdir? Thinking about that lead me to the conclusion that the
config file can only be read after finding the correct WC root, and
then the corresponding config file can be in $FSVS_CONF.
But maybe I just don't understand your needs ... why do you want to
separate them?
Regards,
Phil
--
Versioning your /etc, /home or even your whole installation?
Try fsvs (fsvs.tigris.org)!
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
