DAR - Disk ARchive

I got hold of 3.3.8 in a contributed repository, so I am closer to the
latest release now.

My tests:

Test1:

#!/bin/bash
dar -V
echo "Dar exit code is: $?"

Result Test1:
dar version 2.3.8, Copyright (C) 2002-2052 Denis Corbin
Long options support : YES

Using libdar 4.4.3 built with compilation time options:
Libz compression (gzip) : YES
Libbz2 compression (bzip2) : YES
Strong encryption : YES
New Blowfish implementation: YES
Extended Attributes support: YES
Large files support (> 2GB): YES
ext2fs NODUMP flag support : YES
Special allocation scheme : YES
Integer size used : unlimited
Thread safe support : YES

compiled the Mar 28 2009 with GNUC version 4.3.2 [gcc-4_3-branch revision
141291]
dar is part of the Disk ARchive suite (Release 2.3.8)
dar comes with ABSOLUTELY NO WARRANTY; for details
type `dar -W'. This is free software, and you are welcome
to redistribute it under certain conditions; type `dar -L | more'
for details.


Dar exit code is: 1


Test2:
dar -c "$BACKUP" -R "/" -D -y5 -m 150 -g var/lib/mysql

Result Test2:
Dar exit code is: 0
Archive created correctly.

Test3:
dar -c "$BACKUP" -R "/" -D -y5 -m 150 -g /var/lib/mysql

Result Test3:
Parse error on command line (or included files): Cannot add an absolute
path
Dar exit code is: 1
No archive created.

So the bug I experienced in the former 3.3.6 seemed to be fixed in 3.3.8.
dar -V remains wrong but is not very important.