Hey all,
I think the "working directory" is somewhat misleading here. The
chdir $trunkdir
is executed correctly in all testcases I've seen (there could still be a
catch for the possibility that chdir doesn't work right but I don't see
that happen at the moment).
After checking out the trunk to $trunkdir (the failing cp call in the
bug reporter's first mail has been replaced by 'svn co') the script
changes into $trunkdir and goes on with the SDCommon::writeCfg which
needs to run in $trunkdir (before that we could check if PWD really is
$trunkdir).After all the perl script ends and of course remains in the PWD of the shell where it was invoked. You cannot change the working directory of a parent process (the perl script is a sub-process of your shell). So, in the last message "Your working directory is..." the "working directory" doesn't mean PWD but the directory you can work with since there your checkout (trunk) is to be found. Bottom line: we should consider checking if 'chdir $trunkdir' was really executed before calling SDCommon::writeCfg but the user will always remain in the directoy (s)he was when starting svn-whatever. Hauke ...who hopes he didn't misunderstand everything on his own... :)
signature.asc
Description: Digital signature
