On Thu, 2007-12-13 at 10:49 +0100, Thorsten Schöning wrote: > into the normal config for SCMBug. A Zip-file decompressed in some > directory by the user with maybe changing some configuration is a more > easy way do distribute SCMBug, in my oppinion. A checkout from CVS or > Subversion should be more elegant, too.
I see where you are going with this. We could not use absolute paths in the .pm files and call the hooks with ' perl -L<installation_path>'. (Remember ??? Having a config option won't help us here. We still need to call the hooks to start the glue). It would be easier for a user to change the installation path in the hooks, and also easier for a user to break the installation path in the hooks, and it doesn't solve the problem that a single absolute installation path needs to be agreed on beforehand. I'd rather not use an environment variable, since that relies on the user setting the variable. I'm becoming more convinced we should install in C:\Scmbug.
signature.asc
Description: This is a digitally signed message part
_______________________________________________ scmbug-users mailing list [email protected] http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
