| 2010-10-03 23:28:46 |
Dan MacNeil |
description |
if you delete /var/www/mvhub/$USER/conf/nsp.conf
or whatever $MV_CONFIG_FILE is pointing to,
...app-mvhub/project-tools/bin/mv_update_development
breaks because it is used to get BASE.dir and other things.
The assumption is that if nsp.conf is missing for a user , some other user is running mv_update on behalf of a new user.
apart from this bug, this kludge makes the code awkward and hard to follow.
possible solutions:
gobal /etc/mvhub-dev.conf
[PATHS]
base=/var/www/mvhub/
unique_sub_dir=$USER
appt-mvhub/project-tools/templates/template.conf |
if you delete /var/www/mvhub/$USER/conf/nsp.conf (or whatever $MV_CONFIG_FILE points to) because the file is broken and you'd expect mv_update_development to just regenerate it, you will be disappointed.
app-mvhub/project-tools/bin/mv_update_development breaks because the conf file is used to get BASE.dir and other things.
The assumption is that if nsp.conf is missing for a user , some other user is running mv_update on behalf of a new user.
apart from this bug, this kludge makes the code awkward and hard to follow.
possible solutions:
gobal /etc/mvhub-dev.conf
[PATHS]
base=/var/www/mvhub/
unique_sub_dir=$USER
appt-mvhub/project-tools/templates/template.conf
|
|
