>If I get it working, would you include it ?
Absolutely.
>We would need to link against the libtar.a from tar 1.13.19 alpha though.
>
>Would that be a problem ?
Not if it's done right :-).
I'd suggest something like this:
* Add library tests to configure.in ala the readline ones to see if
libtar is available (I can help if you've never had the joy of
working with autoconf).
* That will define (or undef) HAVE_LIBTAR which can be used in
the code to make the calls or not.
* Appropriate changes need to be made to client-src/Makefile.am to
include libtar on the calcsize build line, if available (again,
steal the template from readline).
* If it's not there already, the appropriate changes to pass the
exclude list from planner to calcsize need to be added. This should
just be a matter of stealing whatever is done in sendsize.
* Calcsize needs to get the exclude option from the packet. Again,
stealing the code from sendsize would be appropriate.
If it is not build with HAVE_LIBTAR it should whine (not sure if
this should be fatal or not -- I'm guessing not, just a warning).
* Appropriate libtar calls need to be made to process the exclusions.
* Finally, I think a dumptype option should be added to control
whether calcsize is used ("calcsize <boolean>", default is "no").
I'm not sure what should happen if program is not "GNUTAR", or if
it appears to be a Samba entry.
> Gerhard
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
