[pkg-bacula-devel] Contribution

[Sven Hartge]

On 14.09.20 16:21, Carsten Leonhardt wrote:

> Here starts one of our previous discussions about libs3:
> 
> https://alioth-lists.debian.net/pipermail/pkg-bacula-devel/2020-June/003017.html
> 
> I've sent an ITP for it:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962918
> 
> Nobody complained there. The next step would be to create a package good
> enough to upload to unstable, or at least experimental. Then the package
> needs to clear the NEW-queue by getting approval by the FTP-masters.

Some hints on libs3 for Bacula:

I tried (privately) to package the library as private library for bacula
in /usr/lib/bacula and /usr/include bacul instead of the normal
/usr/lib/$(ARCH)/ location and change the name to something like
"libbaculas3" but the build system and the sources themselves fought me
every inch.

In the end I gave up because I had reached my limit of knowledge of
packaging libraries.

Why a private library? Because the libs3 Bacula needs is a special fork
by Bacula Systems and there is already a conflicting libs3 in Debian.

Why the rename? To prevent any problems with the linker possibly finding
two different libs3.so in the system, which would lead to problems.

So getting the libs3 code pummeled into a shape to accept its new
location and name would be a first step.

Getting the Bacula source to accept that library is then the second hurdle.

Grüße,
Sven.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-bacula-devel/attachments/20200914/1268bcec/attachment.sig>