[Dar-libdar_api] Re: dar_manager API

[Denis C. <dar...@fr...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Johnathan Burchill wrote:
| Hi Denis,

Hello Johnathan,

[...]

|>
|>Well, maybe I don't properly understand your remark, but, if this is
|>called from within add_archive() directly, what would you give to
|>add_archive(), a filename and path? right? So you cannot use an
|>catalogue from memory. Suppose you make a backup and want to add it
|>automatically to a dar_manager database. If using a filename, you will
|>not be able to use the catalogue in memory but instead will have to load
|>it from just written file...
|>
|
|
| The point is that there is nothing in the API which lets me get access
to a
| catalogue. I expected add_archive to accept a pointer to an archive
object,
| or an archive object to have an accessor to its catalogue which can
then be
| passed to add_archive. The macro_tools_get_catalogue() function is not
| actually part of the public API, and a given archive's cat member is
| private.

OK, I see now. Yes, this is a problem that can be solved by replacing
the "catalogue" argument with a "archive" argument (and appropriated
adaptation within the call). I will fix that, thanks for feedback.


Back to your other remark where you ask why dar_manager relies on dar
command-line and not directly on libdar? The reason is that dar_manager
must do the command-line parsing exactly as dar does, so if I don't want
to duplicate this dar code in dar_manager, I must share it between
theses two programs, but I cannot share it through libdar because libdar
must not receive such command-line related functions. I could, yes, link
dar_manager with the dar's command_line.o object file outside of libdar,
but that would not bring any improvment, just it would avoid creating a
shell from where to run dar.


|
| Regards,
| JB
|
|

Cheers,
Denis.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFC87ywpC5CI8gYGlIRArAoAKCpJ+rWerGMUDGviue0vDmUxuOIxgCfWqgy
uZYZK45QbjRA7jiygZgaoFk=
=JkSO
-----END PGP SIGNATURE-----