Hello,
I'd like to bring you up to date on a few changes we will be making shortly:
- Bacula source repository:
Our source code repository is SVN on Source Forge. In the next few weeks we
will be converting the bacula, gui, and regress parts of the SVN over to use
git. Note: the SVN will continue to contain docs and rescue. The git source
is currently available on both Source Forge and on Github.
You can get a copy of the SF git repository in the directory "bacula" in the
current directory with:
git clone git://bacula.git.sourceforge.net/gitroot/bacula
For the moment, this repository may lag a few commits behind the SVN, but
shortly, it will be the main repository and the SVN will no longer contain
bacula, gui, and regress.
You can also clone a copy from Github with:
git clone git://github.com/bacula/bacula.git bacula
When we shutdown the SVN, the developers/submitters will push to the Github
repository -- normally on branches. This will ensure that the main repository
remains more stable, and it will make it enormously simpler to merge
developer's/submitter's code.
Within a week, I will try to have some git documentation in the Developer's
guide.
- Source Forge User Interface:
Source Forge has redone their user interface, and in my opinion, it is one of
the worst Web user interfaces for downloading project files that I have ever
seen. Even simple web file listings are better GUI than what they have come
up with. Their new user interface not only makes it hard for users to find
and download what they want, but it puts a very bad image forward for Open
Source projects. Too bad.
As a consequence, we have modified the bacula.org Downloads -> Current Files
page to present a more easily readable version of what we have released to
Source Forge. Very likely we will be moving off of Source Forge in the next
couple of months.
- Bacula rpm binaries:
I have recently been looking at the Bacula packaging in more detail, and I am
considering making the following changes:
1. Eliminating the rescue rpm and releasing it as a tar file only.
2. Ensuring that all distributions can build bat and that bat is by default
included in the release.
3. Removing the bat rpm (will be automatically included).
4. Eliminating the mtx rpm. This is now available on all distros, and if not
it is easily build from source using depkgs.
5. Moving the pdf and html docs into a separate rpm release rather than
including it in each release.
6. Making Bacula work "out of the box" in almost all cases. Current rpm
installs require conf file tweaking.
7. Removing rpm support for most of the very old systems (they can always
be built from source).
All the above should help us simplify the spec files, and thus produce better
rpms that have fewer problem.
- Bacula conference:
The first conference devoted to Bacula, to the best of my knowledge, is being
hosted by dass IT, a Bacula professional support company, in Germany. I'll be
there to make a small presentation and answer questions.
See: http://www.bacula-konferenz.de/welcome-3?set_language=en
Best regards,
Kern
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
|
