Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to email@example.com.
Tony Hoyle wrote: > David Somers wrote: > >> It looks fine, but, some entries from my $CVSROOT/cvswrappers are missing >> (*.xpm, *.Z ). >> >> Also, I changed $CVSROOT/cvswrapper to add a new entry for *.dvi... the >> change was committed and the server said it rebuilt the admin files, but >> this entry is also missing. >> >> However, the server does seem to be aware of these entries (for a command >> like ls) ... but they are missing from cvs info cvswrappers. > > The output is a dump of what the client sees as its current > cvswrappers.. it's exactly the same information that the cvs commands use. > > ls doesn't use cvswrappers. True... but I wanted to see what the sever reported the wrappers to be > You can really only tell by doing an add or > import. Also try getting the server-side list (info -s cvswrappers) & > see if they're there. Ah. -s. Right. That was my mistake. I'm still trying to get my head around cvs info. So when the client sets the kopts, does it do so based on just the local cvswrappers, or local+server cvswrappers... if the latter, then wouldn't it make more sense for cvs info -c cvswrappers to return a union of local+server (since that is what the client acts on). > btw. AFAIK xpm files are text (C structures). I had some .xpm files that were binary... can't remember exactly where they came from...but they were not the usual xpm files... this just goes to show that you can't really judge a file from its extension. -- David Somers VoIP: FWD 622885 PGP Key = 7E613D4E Fingerprint = 53A0 D84B 7F90 F227 2EAB 4FD7 6278 E2A8 7E61 3D4E