Closed salarkhan closed 10 years ago
Correction: how do we know where to look to invoke pear
if i'm correct it's existence in the path should allow us to just call it as if it were a native application. i.e. pear
should be a recognized command if it is installed correctly. (which we should be okay on since we are gonna push it to brew) that said i'm usure if the bulk to the calls should in pre-commit or if we should just have one line for the pre-commit that calls like pear do-the-usual-things
and in do-the-usual-things have our current list of commands. Point to ponder: Keeping the commands separate ensures old git repos will have our updates as the commands will not be tied to each repo.
also we can test this for the moment with PATH=$PATH:.
Closed via #34
This is the final step before MVP. WOOP.
If we can't control where the user installs pear, how can we know how to invoke it?