Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


Hi Norbert, *,

On Fri, Jul 22, 2011 at 3:47 PM, Norbert Thiebaud <nthiebaud@gmail.com> wrote:
[...]
Caveat: Like tml_ I don't consider myself a 'Mac' developer... just a
Dev that happen to own a Mac.

That being said, Christian is the person that need convincing.

Oh, I don't consider myself any more Mac developer than you - I happen
to have a PPC with 10.4 on it, so I'm affected (and I definitely won't
update it to 10.5)

I happened to be quite involved of getting rid of external
dependencies on Mac, to compile against the SDK, but that's about it.
Apart from a few bugfixes here and there and making it possible to
uses internal python, I haven't been involved in any actual porting
efforts.

I just find that "drop it because it is old" is not enough reason to
drop 10.4 support.

And raising it to 10.5 won't help anything if you want to use 10.7
features. You then have to provide different codepaths as well, and
need runtime detection for that unless you want to release separate
builds for different versions of Mac OS X - so where's the point?
Where's the benefit of lifting the baseline to 10.5?

The only effect is that you drop support for 10.4 - but I fail to see
any positive effect (apart from the builder not having to install an
"old" version of XCode that comes with the 10.4 SDK - but that again
doesn't count as a reason for me)

ciao
Christian

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.