[binarycloud-dev] CVS missing ./core/ directory

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

Alex:

It got kinda hectic round quittin' time, I didn't get to
your emails on the CVS "problem", and since I use IMAP
at home and POP at work, I don't have them.

BUT, from what I remember:

1.  No file, no directory that is named "core" checks out.
	I co'ed from home in a bare directory and then
	[jef@localhost tmp]$ find . -name Debug.php
	[jef@localhost tmp]$ find . -name init     
	./r2/binarycloud/base/init
	[jef@localhost tmp]$ find . -name core
	[jef@localhost tmp]$ 

	But I think you knew this.  This must be
	some "feature" of CVS, to avoid core dumps

2.  I can't remember exactly what the second question was,
	but I first co'ed in a place in my home directory
	for my "pristine" cvs place.  Then I make in
	the MYPLACE/r2/binarycloud directory to see
	if there are any errors/problems.  Then I copy
	MYPLACE/r2/binarycloud to /usr/local/binarycloud
	and make in /usr/local/binarycloud.  I have to
	make again, because of the self-generated stuff
	such as in prepend.php which ends up defining

define('BC_PATH', '/home/jef/bc/r2/binarycloud/build/en');

	instead of

define('BC_PATH', '/usr/local/binarycloud/build/en');

	where the "development" thingy is.
	So, I have to do a second make, and cannot just
	copy and run...  Yea, I could copy and probably
	edit and then run, if I knew for sure what to
	edit (anything besides prepend.php???).

Maybe I am being redundant, and I am not quite sure
what the second question was.  I hope this helps.

As far as I know, there is only the problem of no
core directory.  And as said, I am still humping along
because I grabbed the ./core/* directory out of the tarball.

PS:  I don't know cvs very well at all.  Is it possible that
	the "filtering" of "core" out can occur on the client
	side, and not your side?

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