[cvsnt] binary files

[Victor A. Wagner Jr.]

OK, it's been 14 hours of pain in the ass and I'm STILL not getting stuff 
to work
I have NO idea what the heck has gone wrong with CVSNT (2.0.41) but this is 
REAL tiresome.
I _finally_ manage to get  cvswrappers setup with the -m 'COPY' and I'd 
like to kill the idiot that thinks that sqotes are required around COPY, so 
now I can actually import stuff correctly on the server to the 
repository.  but NOW I get some stupid warning about  -m not supported 
remotely; ignored when I use remote machines.

oh, and I had to empty my cvsroot and re-init, then put cvsignore and 
cvswrappers back in before I could get it to quit bitching about "can't get 
lock on  modules,v"....and I STILL get it if I'm not going directly to the 
repository  /repository   instead of  :pserver:............../repository

I think all the enhancements going it are great, but how about getting back 
to basics and fixing stuff so we can possibly import a project that has 
both text and binary files!!!

yes, I'm angry, it's 4 f**king AM and I've trying to fix this damned thing 
since 2PM

I've been using RCS since 1985 and this is working a LOT less well for 
simple shit.
I'm very happy that we can handle UNICODE, but FIX THE DARNED BINARY FILE 
PROBLEM !!!!!!!!!!

some more things.... how am I supposed to run repositories on different 
"drives" on 'doze without the person accessing it needing to know about my 
drive letters?
why won't setting the prefix allow one to have / as the repository?... i.e. 
why does the user have to know the directory name?
any chance we'll ever get aliases for the repositories?


I apologize for the language because I'm tire...but I'm also VERY 
frustrated.  this junk USED to work (when the hell did we start 
needing   -m  to handle binary files anyway?  where the hell did -state 
go?  these don't all look like improvements to me.


Victor A. Wagner Jr.      http://rudbek.com
The five most dangerous words in the English language:
               "There oughta be a law"