#9827: tripwire-2.4.3.6
-------------------------+-----------------------
 Reporter:  bdubbs@…     |       Owner:  bdubbs@…
     Type:  enhancement  |      Status:  assigned
 Priority:  normal       |   Milestone:  8.2
Component:  BOOK         |     Version:  SVN
 Severity:  normal       |  Resolution:
 Keywords:               |
-------------------------+-----------------------

Comment (by bdubbs@…):

 2017-10-01 Brian Cox <[email protected]>
    * Update version to 2.4.3.6
    * Fix & expand tests in Perl acceptance test framework
    * Fix & expand twtest unit tests, & rework unit test mini-framework so
 they’re referenced by name, not some numeric ID, and list tests as
 “skipped" if they don’t make any test assertions.
    * Add configure options to enable coverage, profiling, & use
 /dev/urandom as RNG (all off by default)
    * Add a ‘list’ make target to list all make targets
    * Remove dead code & add test coverage per gcov+lcov results
    * Fix various memory issues pointed out by valgrind
    * In examine-encryption mode, better reporting (& nonzero exit) if we
 can't find a keyfile for the examined file.
    * More exception handling around individual objects & init/IC as a
 whole, since there have been occasional reports of uncaught exceptions
 during init or check, and so far haven’t been able to repro or figure out
 what circumstances it occurs under. (e.g. Github issue #25)
    * Tweak install.sh so it can be run directly, not just thru 'make
 install' if you want. (Github issue #26)
    * Improve native (non-Posixy) path handling on platforms that need it
 (DOS, AROS, RISC OS, Redox)
    * New platforms:  MirOS BSD, Bitrig, LibertyBSD, RISC OS, Redox
    * Add default policies for HP-UX & various BSDs

--
Ticket URL: <http://wiki.linuxfromscratch.org/blfs/ticket/9827#comment:2>
BLFS Trac <http://wiki.linuxfromscratch.org/blfs>
Beyond Linux From Scratch
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-book
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to