Forcing binary behavior

I am running CVSNT 2.5.03 and I'm having a problem getting
CVSNT to treat 
certain file types as binary.  I'm hoping I can force this
behavior, but 
after reading the docs and trying a bunch of things I still
can't get this 
to work.  When I build a windows binary I end up with an exe
or dll and also 
a map and pdb file.  I check all the files into CVS: exe,
map, pdb.  It 
treats the exe and pdb the way I would like it to treat
them, as binary 
files.  However, the map file it appears to treat as text. 
I expect this 
behavior by default since I'm guessing .map is not
registered as a binary 
file type.  However even after specifying -kb or -kB it
still appears to 
treat the file as text.  And I say this because when I
update the map file 
and do a cvs diff it spews out a ton of diffs.  What I'm
looking for is for 
CVSNT to treat the map as it does the exe and pdb and when I
do a diff just 
indicate whether the files are different or not but don't
actually attempt 
to show the diffs.  Is there a way to get this behavior?

Thanks,
Nick 


_______________________________________________
cvsnt mailing list
cvsntcvsnt.org
h
ttp://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt

Nick Duane wrote:
> What I'm looking for is for 
> CVSNT to treat the map as it does the exe and pdb and
when I do a diff just 
> indicate whether the files are different or not but
don't actually attempt 
> to show the diffs.  Is there a way to get this
behavior?

There is a good chance that retrieving the map file from CVS
will lead 
to a corrupt version of the file at this point.  Use caution
if you need 
to rely on that file.

See the cvswrappers (server config file in the CVSROOT
directory of your 
repository) for information on how to set files to default
to binary.

See the add command to learn how to do this at the time they
are added.

See the update command to learn how to change the current
attributes 
going forward for existing files.

Also note there are some who argue that derived files (exe,
dll, etc -- 
anything that is generated from compiling source) do not
belong in CVS. 
  Others say special revisions do (e.g. releases).  I can
agree 
arguments in either direction, depending on the situation.

Regards,

-- 
Glen Starrett
Technical Account Manager, North America
March Hare Software, LLC

http://march-hare.com/c
vspro/
_______________________________________________
cvsnt mailing list
cvsntcvsnt.org
h
ttp://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt

Nick Duane wrote:
> I am running CVSNT 2.5.03 and I'm having a problem
getting 
> CVSNT to treat certain file types as binary.  I'm
hoping I 
> can force this behavior, but after reading the docs and

> trying a bunch of things I still can't get this to
work.  
> When I build a windows binary I end up with an exe or
dll and 
> also a map and pdb file.  I check all the files into
CVS: 
> exe, map, pdb.  It treats the exe and pdb the way I
would 
> like it to treat them, as binary files.  However, the
map 
> file it appears to treat as text.

A .map file *is* a text file, so what's the problem?

In any case, why are you storing these artifacts? Store the
source code,
and let VS regenerate the .exe, .pdb and .map. If you are
concerned that
re-generated .map and .pdb files won't match a rebuilt .exe
checked out
from a tag, then archive the .map and .pdb files along with
your master
copy of the .exe file.

> actually attempt to show the diffs.  Is there a way to
get 
> this behavior?

cvs diff --brief

will just show whether or not they have changed.

-- 
Jim
_______________________________________________
cvsnt mailing list
cvsntcvsnt.org
h
ttp://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt