|Wed 1998-10-28 Philip Guenther <guenther(_at_)gac(_dot_)edu> list.procmail
| principle holds: unofficial releases just make things complicated.
| Plus, if some people have a hard time getting their sysadmins to
| install 3.11pre7 because its preceived to be a 'beta' release, how much
| more difficult would it be to have them install an unofficial release?
| Does that mean that if I was to distribute a patched version of procmail,
| I would have to include comments in each source file documenting my
| changes, or would a mention in the HISTORY file be enough?
I would say that "documenting changes" with suffifent detail
can be made to separate History file (I would use Emacs ChangeLog
with C-x 4 a or M-x add-change-log-entry)
| definitely think that we ought to find out what's up with Stephen
| before anyone makes a release of their own.
I second to that.
| Once we do know more, unless he [Stephen] announces an imminent
| reappearance, I'm planning on making availible a "3.11pre8" release (or
| whatever it gets called) incorporating fixes to the known bugs in
| procmail (one in formail, the leading-newline regexp-match problem, a
| buffer overflow in procmail's argument processing, and the
| BSD-realloc() efficiency problem). If that appears to work for testers
| I would then make a non-pre release and see if it can be incorporated
| into software distributions like Redhat's, if just to stamp out 3.10.
| After that, I'll be looking at some enhancements (more memory
| managements changes, LMTP, SWITCHRC, PREMATCH, MIME splitting for
| formail), but that's a ways away.
Exellent ideas. Would it be possible for you Philip to set up a CVS server
for code management? It would be lot easier to manage different patches
and fixes from all over the world. And in case SRB reappears from void,
the changes would be nicely available in CVS server.
Here are pointers from my Emacs page:
[#cf] = connection failed during last link check.
9.4 CVS source and manuals
http://www.cyclic.com/ (Unix, NT ports)
Win GUI: http://www.digapp.com/maccvs/
Win GUI: http://www.freiburg.linux.de/~wxxt/
See also remote control program: http://www.orl.co.uk/vnc/
Mailing List: <info-cvs-request(_at_)gnu(_dot_)org>
http://www.codefab.com/codefab/CVS.html ...stuff is seriously outdated
http://www.iki.fi/liw/texts/cvs.html (Finnish only)
Samba and CVS
just remember to use your system trace tool:
strace, ktrace, truss, par or whetever its called
Inroduction to cvs
very short guide to cvs