This Git::Wrapper newbie spent time untangling two Git::Wrapper behaviours to understand why git->clone wasn't doing what he expected.
Number 2: I assumed from the outset that a git->clone command would execute in the directory specified in Git::Wrapper->new($dir). It wasn't until I ruled out all other possibilities that I finally questioned this assumption and realised the normal behaviour is for git->clone to execute in the cwd. The assumption I made may be peculiar to my psychology but, if it isn't, it may help other users of Git::Wrapper if the cpan/module documentation makes clear just what that initial directory is and, more importantly, is not used for, i.e., whether some/most/all commands actually execute in the cwd.
These teeting problems aside, thanks for a great module.
This Git::Wrapper newbie spent time untangling two Git::Wrapper behaviours to understand why
git->clonewasn't doing what he expected.Number 2: I assumed from the outset that a
git->clonecommand would execute in the directory specified inGit::Wrapper->new($dir). It wasn't until I ruled out all other possibilities that I finally questioned this assumption and realised the normal behaviour is forgit->cloneto execute in the cwd. The assumption I made may be peculiar to my psychology but, if it isn't, it may help other users of Git::Wrapper if the cpan/module documentation makes clear just what that initial directory is and, more importantly, is not used for, i.e., whether some/most/all commands actually execute in the cwd.These teeting problems aside, thanks for a great module.