Bacula patches
Kern Sibbald <[email protected]> 07 Sep 2003 18:53:59 +0200
| Newsgroups | gmane.comp.sysutils.backup.bacula.announce |
|---|---|
| Message-ID | <1062953639.15483.314.camel__3412.68554698235$1062953777@rufus> |
Hello,
Recently someone asked me about patches that
I produce from time to time. The question was
whether or not I would release updated download-able
source containing the patches.
My answer was no because it takes me 4-6 hours
(and sometimes more) to prepare a release. However,
I have for quite some time been thinking about
patches because I am not at all happy about my
current way of distributing them (emailing them
to the list).
Finally, today, I came up with an idea that will
improve things a lot for those of you who may want
to apply the patches I generate. The idea consists
of two parts:
1. All patches will now begin with the release number
of Bacula to which they apply. It will be followed
by a unique sequence number starting at 1, then
be followed by one or two keywords. In addition,
inside the patch file, at the top, I will put a
brief description of what the patch does and
instructions on how to apply it. For example,
the first patch for Bacula version 1.31a is
named:
1.31a-1-bls.patch
and the top of the file contains:
This patch fixes bls so that it can list
files backed up from a Windows machine.
Apply with:
cd <bacula-source>/src/stored
patch -p0 <1.31a-1-bls.patch
cd <bacula-source>
make
...
2. I will make all the patches download-able from
SourceForge. They are to be found under the
heading: bacula-patches/1.31a
This procedure has the advantage that it doesn't take me
too long to upload and release the patches, and you can
immediately see all the patches at any given time are
available, and you can decide which ones to apply and
which ones you don't apply.
If patches for Bacula 1.31a interest you, please take
a look at the Bacula main page on Source Forge, and
you will find that I have uploaded 8 patches. Please
be very careful if you apply any of these patches because
they are generally not tested.
If I missed any patches that I have previously sent out
for Bacula 1.31a, please let me know. From this point on,
I will be sure to release all patches.
Best regards,
Kern
PS: I only have a few minor things to implement for Bacula
1.32, if you have the time and inclination, you might
want to pull the latest Bacula from the CVS. In any
case, I will create and release a beta tar file for the
source sometime next week.
signature.asc
(application/pgp-signature, 189 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQA/W2KnNgfoSvWqwEgRArgRAKCT/yUIQXyZF08iOoAQ4+FuIpW6UQCgiuDr vozfJStVvU+4TFCEg0eV9qI= =tZxH -----END PGP SIGNATURE-----