I use dev-env with gcc/linux. I compiled and installed it as root and (as usual) wanted to configure the user-specific settings as a normal user. But the devcfg tool needs write permission to the DEVENVINSTALL directory - so configuration as a normal user is not possible, that means
a) Each user needs to install his own "private" version of dev-env.
or
b) Each user has to use the same base-directory.
Am I right with these assumptions? Is there any way around this? Or did I do something wrong?
Best regards,
Lothar
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Currently, there is no way to change this
behaviour. One possibility to overcome this
problem would be to introduce a new environment
variable, say DEVENVCONFIG, and let it point
to the user's home directory, e.g. ~/bin/environ.
Then only the executables and scripts would
reside in the DEVENVINSTALL directory, and the
configuration files would be placed in the
DEVENVCONFIG directory.
I can do this for the next release, but
this has to wait till after christmas.
Until then, I recommend to install dev-env
into your home directory, e.g. ~/bin.
Regards,
Christoph
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi!
I use dev-env with gcc/linux. I compiled and installed it as root and (as usual) wanted to configure the user-specific settings as a normal user. But the devcfg tool needs write permission to the DEVENVINSTALL directory - so configuration as a normal user is not possible, that means
a) Each user needs to install his own "private" version of dev-env.
or
b) Each user has to use the same base-directory.
Am I right with these assumptions? Is there any way around this? Or did I do something wrong?
Best regards,
Lothar
Currently, there is no way to change this
behaviour. One possibility to overcome this
problem would be to introduce a new environment
variable, say DEVENVCONFIG, and let it point
to the user's home directory, e.g. ~/bin/environ.
Then only the executables and scripts would
reside in the DEVENVINSTALL directory, and the
configuration files would be placed in the
DEVENVCONFIG directory.
I can do this for the next release, but
this has to wait till after christmas.
Until then, I recommend to install dev-env
into your home directory, e.g. ~/bin.
Regards,
Christoph