There's also a packaged based on Johan Billing's CrashMail II tosser/scanner, but that appears to be a little buggy.
There are some fixes for Crashmail II in the Debian package (which
I am now
the maintainer for); some fixes for 64 bit issues as well as a fix
for a build
issue on GNU/kFreeBSD. I've been thinking of ways to make at least
those fixes
more generally available, plus there are the build warnings to take
care of...
I've also added a simple test suite (using roundup, http://bmizerany.github.com/roundup/),
which turned up another integer-size-bug in crashwrite.c (which would generate invalid packet filenames on 64bit systems).
There are some fixes for Crashmail II in the Debian package
(which I am now the maintainer for); some fixes for 64 bit issues
as well as a fix for a build issue on GNU/kFreeBSD. I've been
thinking of ways to make at least those fixes more generally
available, plus there are the build warnings to take care of...
Oh, I have ripped the old build system to shreds and replaced just
about all of it.
There's now a much more standard suite of Makefiles that should be
much easier to maintain,
You can find all my changes at:
http://github.com/larsks/crashmail
None of these changes are distribution specific. At the moment I'm
simply suppressing the build warnings (with -Wno-pointer-sign).
None of these changes are distribution specific. At the moment I'm simply suppressing the build warnings (with -Wno-pointer-sign).
Those warnings are one of the main things I wanted to work on
None of these changes are distribution specific. At themoment I'm simply suppressing the build warnings (with
-Wno-pointer-sign).
Those warnings are one of the main things I wanted to work on
I think they're fixed now. Make sure you grab the 'develop' branch
from Github.
I did, & I also see that you've released another version. (Btw; I can't
seem to find any changelog type entries? At least, not in docs/History.txt...)
07 Feb 13 12:38, you wrote to me:
I've also added a simple test suite (using roundup,
http://bmizerany.github.com/roundup/),
That's an unfortunate name; the 'roundup' package is an issue
tracker and has been in Debian since 2003...
And since Debian is my primary dev platform, that means that using what
you're currently useing for testing isn't particularly useful to me
or to the
packaging...
And since Debian is my primary dev platform, that means that
using what you're currently useing for testing isn't particularly
useful to me or to the packaging...
The "roundup" script is included in the package, and since it's just a shell script I suspect you can use it without a problem.
Calling it "not useful" seems...wrong?
Having a test suite has already flushed out several bugs.
If you're aware of another Bourne shell test harness that's as easy
to use
.... If you're aware of another Bourne shell test
harness that's as easy to use I'm willing to look at alternatives.
Have you looked at shunit2? (http://code.google.com/p/shunit2/) For
me, it
has the advantage of already being available in Debian/Ubuntu so I'll be investigating it in any case...
Lars,
10 Feb 13 11:48, you wrote to me:
.... If you're aware of another Bourne shell test
harness that's as easy to use I'm willing to look at
alternatives.
Have you looked at shunit2? (http://code.google.com/p/shunit2/)
10 Feb 13 11:48, you wrote to me:
The "roundup" script is included in the package, and since it's
just a shell script I suspect you can use it without a problem.
I will be looking at that,
.... So my preference would be for something usable (if not already available) on all of the platforms.
And perhaps I could set a dependency for running the test suite for
there being a bourne shell available
set up, it was pretty easy to adapt! (Btw, I still need to know which email
address you want as your primary one...)
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,049 |
Nodes: | 15 (0 / 15) |
Uptime: | 07:11:25 |
Calls: | 235,751 |
Calls today: | 1 |
Files: | 60,336 |
D/L today: |
45 files (4,030K bytes) |
Messages: | 287,339 |