From: Alex B. <en...@tu...> - 2001-07-06 01:06:58
|
>> Or first thought was to rename ./core/ to ./bccore/. >> Just a thought. Anybody else feel this way for my reasons, >> or other "administrative" reasons. > > Hmm, I think that makes everything messy and adds redundant information to > the structure. If bc core is renamed, consequently init has to be renamed to > bcinit and lib to bclib and... and.. and... > We have that information already in the direcory structure "binarycloud/*". > I like the name "core" caus it is descriptive and simple. But, I see the > problem of bad written scripts that may interpret core/ as a core dump. For > bc scripts this should not be a problem ;) What cvs concerns it can be > overwritten. As far as i remember core is a default cvsignore. yes, it's only a matter of doing a second import for me - I can automate all that with a shell script anyway. which I just did :) _a > My opinion is to leave core/ as is and just be careful with scripts. > > Andi > > > _______________________________________________ > binarycloud-dev mailing list > bin...@li... > http://lists.sourceforge.net/lists/listinfo/binarycloud-dev > -- alex black, ceo en...@tu... the turing studio, inc. http://www.turingstudio.com vox+510.666.0074 fax+510.666.0093 |