[pkg-bacula-devel] Contribution

[Sven Hartge]

On 20.09.20 09:07, Mario Pranjic wrote:

> I guess changing only LIBDIR destination is not good enough.

As I said: The last time I tried fudging the build system of libs3 it
fought me every millimetre of the way.

> What would be a proper way to control location for LIBS during build &
> packaging process?

That is highly dependant on the source. I imagine more invasive patching
of libs3 is needed to get everything to line up, including the change of
the library name itself. Just changing the base path is not enough.

>> The cloud driver *is* available in the community edition. The only (and
>> this is quite a big "only) hindrance is the usage of a special forked
>> libs3 to get it working.
>>
> Does it mean Bacula Enterprise relies on the same libs3 package we are
> talking about?

I don't know.

But Enterprise-level software being what it is, if they (independent of
developer or company) say "you need library X in version Y", then you
have to do so, even it completely subverts the way you administer your
systems.

I personally have opened support cases with companies about this while
using their products and every one of those cases got closed with either
"not a bug, works as expected" or "please install a supported
environment and try again".

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/20200920/2461f006/attachment.sig>