Bacula-users

Re: [Bacula-users] Debian packages

2014-05-10 05:20:10
Subject: Re: [Bacula-users] Debian packages
From: jltallon AT adv-solutions DOT net
To: <bacula-users AT lists.sourceforge DOT net>
Date: Sat, 10 May 2014 11:01:50 +0200

Hmmm....  I assumed Hauke and Luca were taking good care of Bacula in Debian, since I can't possibly do it for the time being.

 

While I understand your reasons (and /opt/bacula is certainly not the worst place to install to), I guess having a unified set of packages for both Bacula Enterprise and Debian would help.

 

Anyhow, for a Debian-based distro, having Bacula back itself up is innecesary and counter-productive, I believe --- the binaries are available at all times from the Archive.

This said, if you need a beta tester / some suggestions or patches for the packages, I can help.

 

Thanks

 

El 2014-05-10 08:10, Kern Sibbald escribió:


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

On 05/10/2014 01:27 AM, Dan Langille wrote:
> Anyone creating Debian packages?
Bacula.org will release them.

We have the binaries packaged already, but

We have two obstacles:
1. Installing a distribution system on bacula.org -- not too hard and in progress

2. I forgot we have to release the build scripts, and our Enterprise build scripts, which is what we used are not appropriate (way too complicated), so we have gone back to the drawing board.  Of course, we could release the binaries without build scripts while we work on them, but that would be in violation of the AGPLv3. By the way, most of the build/install scripts (RedHat, OSX, SuSE, ...) are in the source code, but for Debian and a few other distros they are not.

One more point:
I find the current way of spreading Bacula binaries all over a system to be counter productive for a backup program that should also be able to back itself up including *all* its scripts and conf files.  Thus all our binaries will install Bacula in /opt/bacula/...

Bottom line: if you cannot accept our packaging (used for all Enterprise installations), you will need the packaging scripts to build Bacula yourself.

Best regards,
Kern

 
------------------------------------------------------------------------------
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
&#149; 3 signs your SCM is hindering your productivity
&#149; Requirements for releasing software faster
&#149; Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
<Prev in Thread] Current Thread [Next in Thread>