On Sat, 2008-10-25 at 21:11 +0200, Eric Bollengier wrote:
> Le Saturday 25 October 2008 13:41:15 Ulrich Leodolter, vous avez écrit :
> > On Sat, 2008-10-25 at 11:32 +0200, Kern Sibbald wrote:
> > > Hello,
> > >
> > > For some time now, I haven't really been happy with the Bacula patch
> > > procedure. Basically, when we fix a bug (either from a bug report or
> > > ourselves), we usually generate a patch, post it to the bug report, if
> > > any, and upload it to the Bacula patches area of Source Forge.
> > >
> > > Providing you are subscribed to the bugs database and to the
> > > bacula-patches release notification on Source Forge, you will see these
> > > patches and can apply them if you deem necessary.
> > >
> > > The problems I have with this is that some people may not know about
> > > patches (we see this in bug reports where a problem is already resolved
> > > with a patch), and there is no formal mechanism for developers when
> > > generating a patch.
> > >
> > > We already have more work than we can handle, so any change needs to be
> > > simple and not time consuming for developers, but I am wondering if
> > > anyone has suggestions how to improve this. I can think of a few:
> > >
> > > 1. Change nothing (signing up for bugs and patch notification is already
> > > not bad).
> > > 2. Announce patches to the bacula-devel list
> > > 3. Announce patches to the bacula-devel list and the bacula-users list
> > > 4. Announce patches to the bacula-announce list as well as the other two
> > > lists.
> > > 5. Put patches in the news (time consuming and I doubt that many read
> > > news). 6. Create an rss feed (I doubt that many users use rss, and this
> > > also could be time consuming).
> >
> > Hello,
> >
> > One thing i am missing are patched packages, rpm and also deb packages
> > have a mechanism to include patch files an apply during build process.
> >
> > For most bacula users it would be much easier to apply patches by "rpm
> > -U ..." or "dpkg install ...".
>
> Yes, but you have to build, test and release a package for each disto after
> each patch, this is a *huge* amount of work, we have something like 10
> patches between two releases.
>
> If someone want to build, test and package 10 more often than before for
> free,
> no problem, but i prefere spend my time with new features and bugs hunting.
>
> > Operating systems like RedHat, CentOS, SLES, Debian, ... are always at
> > least one step behind last official version.
> >
> > An official bacula package repository (yum, apt) would be great.
>
> Fedora, debian and ubuntu already provide this kind of repositor, and often,
> they have a backport branch.
>
Sure u right, a lot of work and resources are needed.
Just curious, how will Bacula Systems handle this ?
Includes Enterprise-Class Support patched binary packages for Customers?
Best Regards
Ulrich
> > Only Sourcecode an patches are released to sourceforge (maybe win32
> > binaries too).
> >
>
> Bye
>
> > Best Regards
> > Ulrich
> >
> > > If anyone else has ideas we would like to hear them.
> > >
> > > Best regards,
> > >
> > > Kern
> > >
>
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
|
