- added protection code against bad_alloc exception
- new configure option to bypass libdl test
- removed expected exception list in deci, limitint, real_infinint
and storage modules to improve global robustness
- remove the #pragma implementation/interface directives
which tend today to become obsolete, and seems to be the
cause of compilation problem on (recent) Linux kernel 2.6.7
for example.
- added protection code to report bug conditions
- code simplification for filesystem reading (while performing
backup)
- fixed bug #29 (crash when saving hard link without read
permission)
- fixed code syntax to support gcc-3.4.x
in the process. (More information on tech-pkg.)
Bump PKGREVISION and BUILDLINK_DEPENDS of all packages using libtool and
installing .la files.
Bump PKGREVISION (only) of all packages depending directly on the above
via a buildlink3 include.
All library names listed by *.la files no longer need to be listed
in the PLIST, e.g., instead of:
lib/libfoo.a
lib/libfoo.la
lib/libfoo.so
lib/libfoo.so.0
lib/libfoo.so.0.1
one simply needs:
lib/libfoo.la
and bsd.pkg.mk will automatically ensure that the additional library
names are listed in the installed package +CONTENTS file.
Also make LIBTOOLIZE_PLIST default to "yes".
Provided in PR 23738 by David Simas.
DAR is a Disk ARchiver, for backing-up file systems to disk. It's rather
in the spirit of TAR, with some additions. Notably:
DAR can break up a archive into multiple files, to facillitate
storage on portable media, like CDs or DVDs.
Can perform incremental back-ups against a reference archive, or,
more conveniently, a "catalog" of an archive, which is sort of a
combination of a TAR table-of-contents and a file checksum list.
DAR also supports filtering, so files or directories can be excluded from
an archive, compression, filtered compression, and the inclusion of parity
in archives, to help recover from media errors.
See http://dar.sourceforge.net/