On Thursday 22 November 2007 15.18:34 Brian A. Seklecki (Mobile) wrote:
> > Well, I don't have a Mac, so I cannot resolve the problem, which means
> > that someone must dig into the problem and come up with some proposed
> > solution if you want Bacula and the Mac to co-exist.
>
> I will setup auto-builds w/ the tinderbox.
>
> > Perhaps you either have the config parameters wrong or you are trying to
> > build servers.
>
> This is a simple FD/client-only build. XCode v3.0. MacPPC CPU type
> (non-Intel). Darwin 9.1.0 ("Up to date Mac OS 10.5.1"). Generic dual-G4
> desktop hardware. Nothing special. Newer, but not bleeding edge.
> Generic even.
>
> I *do* also have access to a 10.4.11/amd64 iMac that I can try it on.
>
> The version of XCode may make the biggest difference. "3.0" doesn't
> sound realistic. There's probably an internal version number that they
> hide from people.
>
> > is not the point -- understanding what they have changed or done
> > differently
>
> They have no transparency and no sound releng process.
>
> Also, if they can donate hardware or development resources >:}
>
> > The first part about OS X binaries is true, but no one has reported *any*
> > problems that I remember. Normally if they do, we integrate the fixes.
>
> I was re-thinking it over dinner.
>
> At first it seemed implausible, but now I'm reconsidering it: To a lot
> of users out there, the part of the F/OSS process where you submit your
> bugs & patches back the community is unheard of.
>
> Maybe its that simple.
Yes, we don't receive enough donations to be able to afford all the necessary
hardware -- and I don't have space for it in my house, so we rely on patches.
This all will change over time with Bacula Company because the company will
want to officially support Mac and hence will make the investment in getting
the hardware.
>
> > We have never stonewalled anyone if that is what you are implying -- we
> > just that need carefully documented problems and proposed solutions for
> > systems that we
>
> I was implying that, indeed. I have personally seen stonewalling
> attitude on issues unrelated to portability.
Well, it is *really* rare that we reject patches. Please don't confuse
stonewalling and the fact that all the developers are already totally
overloaded -- we just cannot do everything, and no one is paying us for this
(and very few are donating) so we do as much of the most important parts as
we can and rely on the community to come up with solutions for the rest ...
>
> WRT this issue, as I stated, it seemed inconceivable that I'm the first
> person to report this.
Well, take a look at the mail archives :-)
>
> Anyway, let me see if XCode 3.0 on 10.4.11 has the same problems.
>
> ~BAS
>
> (*) As a policy, it comes down the sewer pipe from Apple themselves.
> They take what they want (per the license terms) and rarely give back.
> They could be donating shiny new MacBook Pro's to each senior developer
> of each major F/OSS project, but they wont.
>
> As a result, they'll always be stuck with 3-4% of the desktop market.
Well, despite that, with a little effort for those who do have the hardware,
with our advice, you should be able to resolve the problem. But just keep in
mind that without the hardware, we are totally "blind".
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Bacula-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/bacula-devel
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bacula-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-devel
