Re: cvs checkout pgsql

Looks like I replied to the wrong thread...here's a repeat...

Seems the CVS server is not working correctly. I just deleted my CVS
tree and did a fresh checkout of the pgsql module. Everything seemingly
went well. After the check out completed, I did:

[gcope(at)mouse pgsql]$ ./configure --with-tcl --with-java --with-python
--with-perl
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking which template to use... linux
checking whether to build with 64-bit integer date/time support... no
checking whether to build with recode support... no
checking whether NLS is wanted... no
checking for default port number... 5432
checking for default soft limit on number of connections... 32
checking for gcc... gcc
checking for C compiler default output... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
./configure: ./src/template/linux: No such file or directory

So, I did, "./configure" which yields the same result. So, thinking
maybe I just had a poorly timed checkout, I did an update. Doing so,
looks like this:
[gcope(at)mouse pgsql]$ cvs -z3 update -dP
? config.log
cvs server: Updating .
cvs server: Updating ChangeLogs
cvs server: Updating MIGRATION
cvs server: Updating config
.
.
.
src/backend/utils/mb/conversion_procs/utf8_and_iso8859_1
cvs server: Updating
src/backend/utils/mb/conversion_procs/utf8_and_johab
cvs server: Updating src/backend/utils/mb/conversion_procs/utf8_and_sjis
cvs server: cannot open directory
/projects/cvsroot/pgsql/src/backend/utils/mb/conversion_procs/utf8_and_sjis: No such file or directory
cvs server: skipping directory
src/backend/utils/mb/conversion_procs/utf8_and_sjis
cvs server: Updating src/backend/utils/mb/conversion_procs/utf8_and_tcvn
cvs server: cannot open directory
/projects/cvsroot/pgsql/src/backend/utils/mb/conversion_procs/utf8_and_tcvn: No such file or directory
cvs server: skipping directory
src/backend/utils/mb/conversion_procs/utf8_and_tcvn
cvs server: Updating src/backend/utils/mb/conversion_procs/utf8_and_uhc
cvs server: cannot open directory
/projects/cvsroot/pgsql/src/backend/utils/mb/conversion_procs/utf8_and_uhc: No such file or directory
cvs server: skipping directory
src/backend/utils/mb/conversion_procs/utf8_and_uhc
cvs server: Updating src/backend/utils/misc
cvs server: cannot open directory
/projects/cvsroot/pgsql/src/backend/utils/misc: No such file or
directory
cvs server: skipping directory src/backend/utils/misc
cvs server: Updating src/backend/utils/mmgr
cvs server: cannot open directory
/projects/cvsroot/pgsql/src/backend/utils/mmgr: No such file or
directory
cvs server: skipping directory src/backend/utils/mmgr
cvs server: Updating src/backend/utils/sort
cvs server: cannot open directory
/projects/cvsroot/pgsql/src/backend/utils/sort: No such file or
directory
cvs server: skipping directory src/backend/utils/sort
cvs server: Updating src/backend/utils/time
cvs server: cannot open directory
/projects/cvsroot/pgsql/src/backend/utils/time: No such file or
directory
cvs server: skipping directory src/backend/utils/time
cvs server: Updating src/bin
cvs server: cannot open directory /projects/cvsroot/pgsql/src/bin: No
such file or directory
cvs server: skipping directory src/bin

So, I'm fairly sure something is awry.

Greg

Unrelated quote:
> I could move docs into $CVSROOT/this/is/a/stupid/directory/structure/docs
> and except for the fact that you already have a copy checked out pointing
> to the old path, a fresh checkout would still place that in pgsql/docs,
> where you've grown used to it being ...
>

You do realize that by moving modules outside of the base project,
you're forcing more work for the masses. That is, if you plan to have
/doc, /pgsql-server, /contrib, etc, people will now have to create a new
.../pgsql directory locally which means, locally, people will have
.../pgsql/pgsql-server, .../pgsql/contrib, etc...why force onto the
developer what CVS should already be doing it. I don't know about you
guys, but when I check out pgsql, I certainly expect everything to be
there. If that's not what I want, then I should be more explicate in
what I pick for checkout.

Just some food for thought...this is a common peeve of mine when people
decide they need to restructure their repository...seems like this is
always done and almost always a poor choice that isn't realized until
it's all done and over with.

Greg