2010-07-19 11:15:43 +02:00
|
|
|
# vim: syn=sh:
|
|
|
|
|
for wr in 0 1
|
|
|
|
|
do
|
|
|
|
|
for bc in 0 1
|
|
|
|
|
do
|
2010-08-24 13:47:41 +02:00
|
|
|
for ais in 0 1
|
|
|
|
|
do
|
|
|
|
|
cd $TESTDIR
|
|
|
|
|
$TESTDIR/rollback || die "rollback failed"
|
|
|
|
|
editrc GL_WILDREPOS $wr
|
|
|
|
|
editrc GL_BIG_CONFIG $bc
|
|
|
|
|
echo "\$GL_ALL_INCLUDES_SPECIAL = $ais;" | addrc
|
2010-07-19 11:15:43 +02:00
|
|
|
|
2010-08-24 13:47:41 +02:00
|
|
|
# ----------
|
|
|
|
|
name "INTERNAL"
|
|
|
|
|
echo|ugc
|
|
|
|
|
name "daemon access for testing repo"
|
make REPO_BASE absolute early
$ENV{GL_REPO_BASE_ABS} is meant to point to the same directory as
$REPO_BASE, except it is meant to be passed to hooks, ADCs and other
child programs. And since you can't be sure where the child program
starts in, this became an absolute path.
Gradually, however, I started using it wherever I needed an absolute
path (mostly in code that jumps around various directories to do stuff).
Which is silly, because there's no reason $REPO_BASE cannot also be made
an absolute, even if the rc file has a relative path.
So that's what I did now: made $REPO_BASE absolute very early on, and
then systematically changed all uses of the longer form to the shorter
form when appropriate. And so the only thing we now use the longer one
for is to pass to child programs.
(Implementation note: The actual change is not very big, but while I was
about it I decided to make the test suite able to test with an absolute
REPO_BASE also, which is why the commit seems so large.)
----
This all started with a complaint from Damien Regad. He had an
extremely odd setup where his bashrc changed PWD to something other than
$HOME before anything else ran. This caused those two variables to
beceom inconsistent, and he had a 1-line fix he wanted me to apply.
I generally don't like making special fixes for for non-standard setups,
and anyway all he had to do was set the full path to REPO_BASE in the rc
file to get around this. Which is what I told him and he very politely
left it at that.
However, this did get me thinking, and I soon realised I was needlessly
conflating "relative versus absolute" with "able to be passed to child
programs". Fixing that solved his problem also, as a side-effect.
So I guess this is all thanks to Damien!
2011-03-18 06:29:52 +01:00
|
|
|
runremote ls -al $TEST_BASE/testing.git/git-daemon-export-ok
|
|
|
|
|
[ "$ais" = "0" ] && expect "ls: cannot access $TEST_BASE/testing.git/git-daemon-export-ok: No such file or directory"
|
2011-10-11 04:40:06 +02:00
|
|
|
[ "$ais" = "1" ] && expect "$USER $USER .* $TEST_BASE/testing.git/git-daemon-export-ok"
|
2010-07-19 11:15:43 +02:00
|
|
|
|
2010-08-24 13:47:41 +02:00
|
|
|
name "INTERNAL"
|
|
|
|
|
echo "
|
|
|
|
|
@leads = u1 u2
|
|
|
|
|
@devs = u1 u2 u3 u4
|
2010-07-19 11:15:43 +02:00
|
|
|
|
2010-08-24 13:47:41 +02:00
|
|
|
@gbar = bar
|
|
|
|
|
repo @gbar
|
|
|
|
|
RW+ = @leads
|
|
|
|
|
RW = @devs
|
|
|
|
|
" | ugc
|
|
|
|
|
expect_push_ok "master -> master"
|
make REPO_BASE absolute early
$ENV{GL_REPO_BASE_ABS} is meant to point to the same directory as
$REPO_BASE, except it is meant to be passed to hooks, ADCs and other
child programs. And since you can't be sure where the child program
starts in, this became an absolute path.
Gradually, however, I started using it wherever I needed an absolute
path (mostly in code that jumps around various directories to do stuff).
Which is silly, because there's no reason $REPO_BASE cannot also be made
an absolute, even if the rc file has a relative path.
So that's what I did now: made $REPO_BASE absolute very early on, and
then systematically changed all uses of the longer form to the shorter
form when appropriate. And so the only thing we now use the longer one
for is to pass to child programs.
(Implementation note: The actual change is not very big, but while I was
about it I decided to make the test suite able to test with an absolute
REPO_BASE also, which is why the commit seems so large.)
----
This all started with a complaint from Damien Regad. He had an
extremely odd setup where his bashrc changed PWD to something other than
$HOME before anything else ran. This caused those two variables to
beceom inconsistent, and he had a 1-line fix he wanted me to apply.
I generally don't like making special fixes for for non-standard setups,
and anyway all he had to do was set the full path to REPO_BASE in the rc
file to get around this. Which is what I told him and he very politely
left it at that.
However, this did get me thinking, and I soon realised I was needlessly
conflating "relative versus absolute" with "able to be passed to child
programs". Fixing that solved his problem also, as a side-effect.
So I guess this is all thanks to Damien!
2011-03-18 06:29:52 +01:00
|
|
|
runremote ls -al $TEST_BASE/bar.git/git-daemon-export-ok
|
|
|
|
|
expect "ls: cannot access $TEST_BASE/bar.git/git-daemon-export-ok: No such file or directory"
|
2010-08-24 13:47:41 +02:00
|
|
|
runremote ls -al projects.list
|
2011-10-11 04:40:06 +02:00
|
|
|
[ "$ais" = "0" ] && expect "$USER $USER 0 .* projects.list"
|
|
|
|
|
[ "$ais" = "1" ] && expect "$USER $USER 12 .* projects.list"
|
2010-08-24 13:47:41 +02:00
|
|
|
runremote cat projects.list
|
|
|
|
|
[ "$ais" = "0" ] && notexpect "testing.git"
|
|
|
|
|
[ "$ais" = "1" ] && expect "testing.git"
|
2010-07-19 11:15:43 +02:00
|
|
|
|
2010-08-24 13:47:41 +02:00
|
|
|
name "add daemon access to bar"
|
|
|
|
|
echo "
|
|
|
|
|
R = daemon
|
|
|
|
|
" | ugc
|
make REPO_BASE absolute early
$ENV{GL_REPO_BASE_ABS} is meant to point to the same directory as
$REPO_BASE, except it is meant to be passed to hooks, ADCs and other
child programs. And since you can't be sure where the child program
starts in, this became an absolute path.
Gradually, however, I started using it wherever I needed an absolute
path (mostly in code that jumps around various directories to do stuff).
Which is silly, because there's no reason $REPO_BASE cannot also be made
an absolute, even if the rc file has a relative path.
So that's what I did now: made $REPO_BASE absolute very early on, and
then systematically changed all uses of the longer form to the shorter
form when appropriate. And so the only thing we now use the longer one
for is to pass to child programs.
(Implementation note: The actual change is not very big, but while I was
about it I decided to make the test suite able to test with an absolute
REPO_BASE also, which is why the commit seems so large.)
----
This all started with a complaint from Damien Regad. He had an
extremely odd setup where his bashrc changed PWD to something other than
$HOME before anything else ran. This caused those two variables to
beceom inconsistent, and he had a 1-line fix he wanted me to apply.
I generally don't like making special fixes for for non-standard setups,
and anyway all he had to do was set the full path to REPO_BASE in the rc
file to get around this. Which is what I told him and he very politely
left it at that.
However, this did get me thinking, and I soon realised I was needlessly
conflating "relative versus absolute" with "able to be passed to child
programs". Fixing that solved his problem also, as a side-effect.
So I guess this is all thanks to Damien!
2011-03-18 06:29:52 +01:00
|
|
|
runremote ls -al $TEST_BASE/bar.git/git-daemon-export-ok
|
2011-10-11 04:40:06 +02:00
|
|
|
expect "$USER $USER .* $TEST_BASE/bar.git/git-daemon-export-ok"
|
2010-08-24 13:47:41 +02:00
|
|
|
runremote ls -al projects.list
|
2011-10-11 04:40:06 +02:00
|
|
|
[ "$ais" = "0" ] && expect "$USER $USER 0 .* projects.list"
|
|
|
|
|
[ "$ais" = "1" ] && expect "$USER $USER 12 .* projects.list"
|
2010-07-19 11:15:43 +02:00
|
|
|
|
2010-08-24 13:47:41 +02:00
|
|
|
name "add foo with gitweb access"
|
|
|
|
|
echo "
|
|
|
|
|
@leads = u1 u2
|
|
|
|
|
@devs = u1 u2 u3 u4
|
2010-07-19 11:15:43 +02:00
|
|
|
|
2010-08-24 13:47:41 +02:00
|
|
|
@gfoo = foo
|
|
|
|
|
repo @gfoo
|
|
|
|
|
RW+ = @leads
|
|
|
|
|
RW = @devs
|
|
|
|
|
R = gitweb
|
|
|
|
|
" | ugc
|
|
|
|
|
expect_push_ok "master -> master"
|
|
|
|
|
runremote ls -al projects.list
|
2011-10-11 04:40:06 +02:00
|
|
|
[ "$ais" = "0" ] && expect "$USER $USER 8 .* projects.list"
|
|
|
|
|
[ "$ais" = "1" ] && expect "$USER $USER 20 .* projects.list"
|
2010-08-24 13:47:41 +02:00
|
|
|
runremote cat projects.list
|
|
|
|
|
[ "$ais" = "0" ] && notexpect "testing.git"
|
|
|
|
|
[ "$ais" = "1" ] && expect "testing.git"
|
|
|
|
|
expect "foo.git"
|
2010-07-19 11:15:43 +02:00
|
|
|
|
2010-08-24 13:47:41 +02:00
|
|
|
name "add gitweb access to bar"
|
|
|
|
|
echo "
|
|
|
|
|
repo @gbar
|
|
|
|
|
R = gitweb
|
|
|
|
|
" | ugc
|
|
|
|
|
expect_push_ok "master -> master"
|
|
|
|
|
runremote ls -al projects.list
|
2011-10-11 04:40:06 +02:00
|
|
|
[ "$ais" = "0" ] && expect "$USER $USER 16 .* projects.list"
|
|
|
|
|
[ "$ais" = "1" ] && expect "$USER $USER 28 .* projects.list"
|
2010-08-24 13:47:41 +02:00
|
|
|
runremote cat projects.list
|
|
|
|
|
[ "$ais" = "0" ] && notexpect "testing.git"
|
|
|
|
|
[ "$ais" = "1" ] && expect "testing.git"
|
|
|
|
|
expect "foo.git"
|
|
|
|
|
expect "bar.git"
|
2010-07-19 11:15:43 +02:00
|
|
|
|
2010-08-24 13:47:41 +02:00
|
|
|
name "add repo baz with description"
|
|
|
|
|
echo "
|
|
|
|
|
@gbaz = baz
|
|
|
|
|
repo @gbaz
|
|
|
|
|
RW = @leads
|
2010-07-19 11:15:43 +02:00
|
|
|
|
2010-08-24 13:47:41 +02:00
|
|
|
baz = \"this is repo baz\"
|
|
|
|
|
" | ugc
|
|
|
|
|
expect_push_ok "master -> master"
|
make REPO_BASE absolute early
$ENV{GL_REPO_BASE_ABS} is meant to point to the same directory as
$REPO_BASE, except it is meant to be passed to hooks, ADCs and other
child programs. And since you can't be sure where the child program
starts in, this became an absolute path.
Gradually, however, I started using it wherever I needed an absolute
path (mostly in code that jumps around various directories to do stuff).
Which is silly, because there's no reason $REPO_BASE cannot also be made
an absolute, even if the rc file has a relative path.
So that's what I did now: made $REPO_BASE absolute very early on, and
then systematically changed all uses of the longer form to the shorter
form when appropriate. And so the only thing we now use the longer one
for is to pass to child programs.
(Implementation note: The actual change is not very big, but while I was
about it I decided to make the test suite able to test with an absolute
REPO_BASE also, which is why the commit seems so large.)
----
This all started with a complaint from Damien Regad. He had an
extremely odd setup where his bashrc changed PWD to something other than
$HOME before anything else ran. This caused those two variables to
beceom inconsistent, and he had a 1-line fix he wanted me to apply.
I generally don't like making special fixes for for non-standard setups,
and anyway all he had to do was set the full path to REPO_BASE in the rc
file to get around this. Which is what I told him and he very politely
left it at that.
However, this did get me thinking, and I soon realised I was needlessly
conflating "relative versus absolute" with "able to be passed to child
programs". Fixing that solved his problem also, as a side-effect.
So I guess this is all thanks to Damien!
2011-03-18 06:29:52 +01:00
|
|
|
expect "remote: Initialized empty Git repository in $TEST_BASE_FULL/baz.git/"
|
2010-08-24 13:47:41 +02:00
|
|
|
runremote ls -al projects.list
|
2011-10-11 04:40:06 +02:00
|
|
|
[ "$ais" = "0" ] && expect "$USER $USER 24 .* projects.list"
|
|
|
|
|
[ "$ais" = "1" ] && expect "$USER $USER 36 .* projects.list"
|
2010-08-24 13:47:41 +02:00
|
|
|
runremote cat projects.list
|
|
|
|
|
[ "$ais" = "0" ] && notexpect "testing.git"
|
|
|
|
|
[ "$ais" = "1" ] && expect "testing.git"
|
|
|
|
|
expect "foo.git"
|
|
|
|
|
expect "bar.git"
|
|
|
|
|
expect "baz.git"
|
make REPO_BASE absolute early
$ENV{GL_REPO_BASE_ABS} is meant to point to the same directory as
$REPO_BASE, except it is meant to be passed to hooks, ADCs and other
child programs. And since you can't be sure where the child program
starts in, this became an absolute path.
Gradually, however, I started using it wherever I needed an absolute
path (mostly in code that jumps around various directories to do stuff).
Which is silly, because there's no reason $REPO_BASE cannot also be made
an absolute, even if the rc file has a relative path.
So that's what I did now: made $REPO_BASE absolute very early on, and
then systematically changed all uses of the longer form to the shorter
form when appropriate. And so the only thing we now use the longer one
for is to pass to child programs.
(Implementation note: The actual change is not very big, but while I was
about it I decided to make the test suite able to test with an absolute
REPO_BASE also, which is why the commit seems so large.)
----
This all started with a complaint from Damien Regad. He had an
extremely odd setup where his bashrc changed PWD to something other than
$HOME before anything else ran. This caused those two variables to
beceom inconsistent, and he had a 1-line fix he wanted me to apply.
I generally don't like making special fixes for for non-standard setups,
and anyway all he had to do was set the full path to REPO_BASE in the rc
file to get around this. Which is what I told him and he very politely
left it at that.
However, this did get me thinking, and I soon realised I was needlessly
conflating "relative versus absolute" with "able to be passed to child
programs". Fixing that solved his problem also, as a side-effect.
So I guess this is all thanks to Damien!
2011-03-18 06:29:52 +01:00
|
|
|
runremote ls -al $TEST_BASE/baz.git/description
|
2011-10-11 04:40:06 +02:00
|
|
|
expect "$USER $USER 17 .* $TEST_BASE/baz.git/description"
|
make REPO_BASE absolute early
$ENV{GL_REPO_BASE_ABS} is meant to point to the same directory as
$REPO_BASE, except it is meant to be passed to hooks, ADCs and other
child programs. And since you can't be sure where the child program
starts in, this became an absolute path.
Gradually, however, I started using it wherever I needed an absolute
path (mostly in code that jumps around various directories to do stuff).
Which is silly, because there's no reason $REPO_BASE cannot also be made
an absolute, even if the rc file has a relative path.
So that's what I did now: made $REPO_BASE absolute very early on, and
then systematically changed all uses of the longer form to the shorter
form when appropriate. And so the only thing we now use the longer one
for is to pass to child programs.
(Implementation note: The actual change is not very big, but while I was
about it I decided to make the test suite able to test with an absolute
REPO_BASE also, which is why the commit seems so large.)
----
This all started with a complaint from Damien Regad. He had an
extremely odd setup where his bashrc changed PWD to something other than
$HOME before anything else ran. This caused those two variables to
beceom inconsistent, and he had a 1-line fix he wanted me to apply.
I generally don't like making special fixes for for non-standard setups,
and anyway all he had to do was set the full path to REPO_BASE in the rc
file to get around this. Which is what I told him and he very politely
left it at that.
However, this did get me thinking, and I soon realised I was needlessly
conflating "relative versus absolute" with "able to be passed to child
programs". Fixing that solved his problem also, as a side-effect.
So I guess this is all thanks to Damien!
2011-03-18 06:29:52 +01:00
|
|
|
runremote cat $TEST_BASE/baz.git/description
|
2010-08-24 13:47:41 +02:00
|
|
|
expect "this is repo baz"
|
2010-07-19 11:15:43 +02:00
|
|
|
|
2010-08-24 13:47:41 +02:00
|
|
|
name "add owner to testing repo"
|
|
|
|
|
echo "
|
|
|
|
|
testing \"sitaram\" = \"this is the testing repo\"
|
|
|
|
|
" | ugc
|
|
|
|
|
expect_push_ok "master -> master"
|
|
|
|
|
runremote ls -al projects.list
|
2011-10-11 04:40:06 +02:00
|
|
|
expect "$USER $USER 36 .* projects.list"
|
2010-08-24 13:47:41 +02:00
|
|
|
runremote cat projects.list
|
|
|
|
|
expect "testing.git"
|
|
|
|
|
expect "foo.git"
|
|
|
|
|
expect "bar.git"
|
|
|
|
|
expect "baz.git"
|
make REPO_BASE absolute early
$ENV{GL_REPO_BASE_ABS} is meant to point to the same directory as
$REPO_BASE, except it is meant to be passed to hooks, ADCs and other
child programs. And since you can't be sure where the child program
starts in, this became an absolute path.
Gradually, however, I started using it wherever I needed an absolute
path (mostly in code that jumps around various directories to do stuff).
Which is silly, because there's no reason $REPO_BASE cannot also be made
an absolute, even if the rc file has a relative path.
So that's what I did now: made $REPO_BASE absolute very early on, and
then systematically changed all uses of the longer form to the shorter
form when appropriate. And so the only thing we now use the longer one
for is to pass to child programs.
(Implementation note: The actual change is not very big, but while I was
about it I decided to make the test suite able to test with an absolute
REPO_BASE also, which is why the commit seems so large.)
----
This all started with a complaint from Damien Regad. He had an
extremely odd setup where his bashrc changed PWD to something other than
$HOME before anything else ran. This caused those two variables to
beceom inconsistent, and he had a 1-line fix he wanted me to apply.
I generally don't like making special fixes for for non-standard setups,
and anyway all he had to do was set the full path to REPO_BASE in the rc
file to get around this. Which is what I told him and he very politely
left it at that.
However, this did get me thinking, and I soon realised I was needlessly
conflating "relative versus absolute" with "able to be passed to child
programs". Fixing that solved his problem also, as a side-effect.
So I guess this is all thanks to Damien!
2011-03-18 06:29:52 +01:00
|
|
|
runremote cat $TEST_BASE/testing.git/config
|
2010-08-24 13:47:41 +02:00
|
|
|
expect "\[gitweb\]"
|
|
|
|
|
expect "owner = sitaram"
|
make REPO_BASE absolute early
$ENV{GL_REPO_BASE_ABS} is meant to point to the same directory as
$REPO_BASE, except it is meant to be passed to hooks, ADCs and other
child programs. And since you can't be sure where the child program
starts in, this became an absolute path.
Gradually, however, I started using it wherever I needed an absolute
path (mostly in code that jumps around various directories to do stuff).
Which is silly, because there's no reason $REPO_BASE cannot also be made
an absolute, even if the rc file has a relative path.
So that's what I did now: made $REPO_BASE absolute very early on, and
then systematically changed all uses of the longer form to the shorter
form when appropriate. And so the only thing we now use the longer one
for is to pass to child programs.
(Implementation note: The actual change is not very big, but while I was
about it I decided to make the test suite able to test with an absolute
REPO_BASE also, which is why the commit seems so large.)
----
This all started with a complaint from Damien Regad. He had an
extremely odd setup where his bashrc changed PWD to something other than
$HOME before anything else ran. This caused those two variables to
beceom inconsistent, and he had a 1-line fix he wanted me to apply.
I generally don't like making special fixes for for non-standard setups,
and anyway all he had to do was set the full path to REPO_BASE in the rc
file to get around this. Which is what I told him and he very politely
left it at that.
However, this did get me thinking, and I soon realised I was needlessly
conflating "relative versus absolute" with "able to be passed to child
programs". Fixing that solved his problem also, as a side-effect.
So I guess this is all thanks to Damien!
2011-03-18 06:29:52 +01:00
|
|
|
runremote ls -al $TEST_BASE/testing.git/description
|
2011-10-11 04:40:06 +02:00
|
|
|
expect "$USER $USER 25 .* $TEST_BASE/testing.git/description"
|
make REPO_BASE absolute early
$ENV{GL_REPO_BASE_ABS} is meant to point to the same directory as
$REPO_BASE, except it is meant to be passed to hooks, ADCs and other
child programs. And since you can't be sure where the child program
starts in, this became an absolute path.
Gradually, however, I started using it wherever I needed an absolute
path (mostly in code that jumps around various directories to do stuff).
Which is silly, because there's no reason $REPO_BASE cannot also be made
an absolute, even if the rc file has a relative path.
So that's what I did now: made $REPO_BASE absolute very early on, and
then systematically changed all uses of the longer form to the shorter
form when appropriate. And so the only thing we now use the longer one
for is to pass to child programs.
(Implementation note: The actual change is not very big, but while I was
about it I decided to make the test suite able to test with an absolute
REPO_BASE also, which is why the commit seems so large.)
----
This all started with a complaint from Damien Regad. He had an
extremely odd setup where his bashrc changed PWD to something other than
$HOME before anything else ran. This caused those two variables to
beceom inconsistent, and he had a 1-line fix he wanted me to apply.
I generally don't like making special fixes for for non-standard setups,
and anyway all he had to do was set the full path to REPO_BASE in the rc
file to get around this. Which is what I told him and he very politely
left it at that.
However, this did get me thinking, and I soon realised I was needlessly
conflating "relative versus absolute" with "able to be passed to child
programs". Fixing that solved his problem also, as a side-effect.
So I guess this is all thanks to Damien!
2011-03-18 06:29:52 +01:00
|
|
|
runremote cat $TEST_BASE/testing.git/description
|
2010-08-24 13:47:41 +02:00
|
|
|
expect "this is the testing repo"
|
2010-07-19 11:15:43 +02:00
|
|
|
|
2010-08-24 13:47:41 +02:00
|
|
|
name INTERNAL
|
|
|
|
|
done
|
2010-07-19 11:15:43 +02:00
|
|
|
done
|
|
|
|
|
done
|