Junio C Hamano [off-list ref] writes:
quoted
+------------
+echo "#"\!"/bin/sh" > ~/test.sh
+echo "make install || exit 125" >> ~/test.sh
+echo "~/check_test_case.sh" >> ~/test.sh
+chmod u+x ~/test.sh
s/install//; let's not set a bad example of installing first and then
testing.
Perhaps also s/~/./g, since it's not a good idea to put temporary
files in $HOME IMHO.
Also, using simple quotes instead of double would simplify the
"#"\!"/bin/sh".
--
Matthieu
On Wed, May 07, 2008 at 08:29:03AM +0200, Matthieu Moy [off-list ref] wrote:
Perhaps also s/~/./g, since it's not a good idea to put temporary
files in $HOME IMHO.
the point is to have it outside the repo. at least i regularly have 'git
clean -f -x -d' in such a script if i don't trust the upstream build
system. ;)
On Wed, 2008-05-07 at 08:29 +0200, Matthieu Moy wrote:
Junio C Hamano [off-list ref] writes:
quoted
quoted
+------------
+echo "#"\!"/bin/sh" > ~/test.sh
+echo "make install || exit 125" >> ~/test.sh
+echo "~/check_test_case.sh" >> ~/test.sh
+chmod u+x ~/test.sh
s/install//; let's not set a bad example of installing first and then
testing.
Perhaps also s/~/./g, since it's not a good idea to put temporary
files in $HOME IMHO.
Also, using simple quotes instead of double would simplify the
"#"\!"/bin/sh".
Hmm. I would have just done "$ cat ~/test.sh" and
then shown the file listing directly.
jdl
Le mercredi 7 mai 2008, Miklos Vajna a écrit :
On Wed, May 07, 2008 at 08:29:03AM +0200, Matthieu Moy
[off-list ref] wrote:
quoted
Perhaps also s/~/./g, since it's not a good idea to put temporary
files in $HOME IMHO.
the point is to have it outside the repo.
Yes. Especially, if the test case is a new one, the scripts that are used
must not have been checked in. Otherwise when bisect will checkout older
versions, the scripts will be removed.
at least i regularly have 'git
clean -f -x -d' in such a script if i don't trust the upstream build
system. ;)