On Montag, 9. September 2013 21:00:17 CEST, Pali Rohár wrote:
On Monday 09 September 2013 20:52:37 Kevin Krammer wrote:
On Monday, 2013-09-09, Pali Rohár wrote:
On Monday 09 September 2013 20:26:27 Thomas Lübking wrote:
On Montag, 9. September 2013 12:55:47 CEST, Pali Rohár
wrote:
...
Wouldn't an env variable make this very easy? E.g. something
like SOME_ENV_VAR=$(pwd)/plugins ./trojita
...
And you want to start trojita with writing all these chars (after
compiling and not installed to system - when you want to test)?
No, I make usage of a very basic shell feature and *once*
export SOME_ENV_VAR=$(pwd)/plugins
then
make && ./trojita
[test]
<arrow up>
[test]
and eventually even can
unset SOME_ENV_VAR
./trojita
[test whether i broke th core or the plugin]
Also every better IDE has support for setting the enviroment when loading a
project.
Leaving aside that this is actually only required when altering the plugins
compared to the installed version and most important:
"lazy developer" does not justify putting even the slightest risk on the user.
If you think this is a problem because the devloper first has to know to set
the variable, trojita.git could contain
trojita.dev*
#!/bin/sh
SOME_ENV_VAR=$(pwd)/plugins `realpath $0`/trojita
Still Jans decision, but you will not read "hardcoding PWD is a good idea" from
me.
Cheers,
Thomas
