[pkg-bacula-devel] Contribution

[Mario Pranjic]

On 9/14/20 10:46 PM, Sven Hartge wrote:
> That is still the case. Bacula Enterprise is something people called "open
> core licensed". Bacula itself is licensed under the AGPL license and fully
> open source.
>
> Bacula Systems SA or Kern Sibbald will port code from the Enterprise
> version to the community version after some time has passed.

> Concerning the Enterprise version supporting more than one S3 provider: As
> far as I know (please don't quote me on that), Bacula Systems have
> redeveloped the cloud/S3 integration in the Enterprise version. That
> change has not yet landed in the community edition.


I checked email conversation with Bacula Enterprise representative and I
see there is several cloud drivers for different cloud providers.
Maybe it is bundled in single package, but they are billed separately.


> libs3 is a generic library external to Bacula, just like libcurl or
> libzstd.
>  
>> If, on the other hand, this cloud driver is actually "general purpose"
>> piece of code to communicate with AWS S3 bucket and it suppose to be
>> used by Bacula "as is", then it makes more sense.
> Only the cloud-driver is Bacula code that just uses libs3. libs3 is *not*
> the cloud-driver per se.
OK, so libs3 is one part. Where is then Bacula cloud driver?

In other words, what was I building in the first place?


BR,

Mario.


-------------- 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/20200915/2e6fcd40/attachment.sig>