[Cvs-syncmail] [ cvs-syncmail-Bugs-717082 ] jar files incorrectly treated as ascii

[SourceForge.net <no...@so...>]

Bugs item #717082, was opened at 2003-04-07 18:57
Message generated for change (Comment added) made by fdrake
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=450019&aid=717082&group_id=47611

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Aslak Hellesøy (rinkrank)
>Assigned to: Fred L. Drake, Jr. (fdrake)
Summary: jar files incorrectly treated as ascii

Initial Comment:
When adding/committing a new jar file to cvs, cvs-
syncmail incorrectly sends a message like this:
------------
Update of /cvsroot/xdoclet/xdoclet2/lib/rngconv/jars
In directory sc8-pr-
cvs1:/tmp/cvsserv14703/lib/rngconv/jars

Added Files:
	rngconv-20030225.jar 
Log Message:
Initial support for XML Schema in XGG (using Sun's 
rngconv)

--- NEW FILE: rngconv-20030225.jar ---
PK
------------
This leads people to think the file was incorrectly added 
as ascii, while it's actually syncmail that incorrectly 
assumes it's ascii.

(jar files are in zip format).


----------------------------------------------------------------------

>Comment By: Fred L. Drake, Jr. (fdrake)
Date: 2003-04-08 14:48

Message:
Logged In: YES 
user_id=3066

This one's my fault to begin with, so I'm assigning it to
myself.
There are a couple of possible approaches to handling this:

1.  Use the "rlog -f comma-v-file" command to get the log
header information from the RCS backend, looking for the
"keyword substitution" field.  Pros:  sticks with something
reasonable close to a "public API" for the system; we don't
have to reach into the actual file.  Also, I've written code
to do this before.  Con:  We need to start up another
process for each syncmail run to get the information.

2.  Parse the information directly from the ,v file.  Pros:
 It's faster; no additional processes to manage.  I know
where I can easily get some code to do this from a public
source.  Con:  We have to deal with the format of ,v files
directly.  Seriously, the ,v format just hasn't changed
recently, and isn't likely to do so.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=450019&aid=717082&group_id=47611