[binarycloud-dev] Something rotten in CVS???

[Justin F. <je...@ey...>]

Alex:

There seems to be something rotten in the CVS.

Now when the tarball first came out, I got that and
installed it at home, and did it dirty, namely let
the un-tarring just write over the current directory
structure, which was, incidentally, an older CVS from
jason's account.

Everything worked perfectly.

This was the situation at work too.

But, I decided to get organized, get my own CVS etc,
and start from scratch with the latest CVS.  So I:

1.  Saved my modules/masters/layouts
2.  Snipped off the /usr/local/binarycloud tree
3.  Snipped off the "bc" tree in my /home/jef where
	I "buffer" the CVS
4.  Went to /home/jef/bc
5.  Got the CVS
6.  couple of edits, (a) force LANGS=en in the Makefile
	and (b) changed the shebang in script that
	let it know php was really in /usr/bin/php
7.  went to ./binarycloud and typed make, - everything OK
8.  copied ./binarycloud (in home tree) to /usr/local/binarycloud
9.  went to /usr/local/binarycloud, changed BCHOME, did make
	and all OK
10. copied the /usr/local/binarycloud/build/en/htdocs/*
	stuff up to the DOCUMENT_ROOT.
11. pointed browser to ..../bcdocs/index.php and got

Warning: Failed opening
'/usr/local/binarycloud/build/en/binarycloud/core/Debug.php' for
inclusion (include_path='.:/usr/share/php') in
./prepend.php on line 33

URG, their ain't no ./core directory.  It is missing in the
place I keep CVS

[jef@dev8 binarycloud]$ pwd
/home/jef/bc/r2/binarycloud/build/en/binarycloud
[jef@dev8 binarycloud]$ ls -l
total 8
drwxr-xr-x    2 jef      jef          4096 Jul  3 15:35 init/
drwxr-xr-x    3 jef      jef          4096 Jul  3 15:35 lib/
[jef@dev8 binarycloud]$ 

nor when I copied the tree to /usr/local/binarycloud
and remade everything, obviously,

[jef@dev8 binarycloud]$ pwd
/usr/local/binarycloud/build/en/binarycloud
[jef@dev8 binarycloud]$ ls -l
total 8
drwxr-xr-x    2 jef      jef          4096 Jul  3 15:41 init/
drwxr-xr-x    3 jef      jef          4096 Jul  3 15:41 lib/
[jef@dev8 binarycloud]$ 

Now, I went back to the tarball that I had used before,
and untarred it again in a ./tmp directory.  There,
after making (or even before), core is in the tarball.

[jef@dev8 tmp]$ find `pwd` -name Debug.php
/home/jef/tmp/r2/binarycloud/base/core/Debug.php
/home/jef/tmp/r2/binarycloud/build/en/binarycloud/core/Debug.php
[jef@dev8 tmp]$ 

After I copied this core directory up to where it belongs
in /usr/local/binarycloud, everything worked fine.

So, the core directory is missing from CVS, and things worked
here before because of the residue from the tarball.  When I
started "virgin" cvs, the missing ./core became evident.

_jef
-- 
Justin Farnsworth
Eye Integrated Communications
321 South Evans - Suite 203
Greenville, NC 27858 | Tel: (252) 353-0722