Am Sonntag, 14. Januar 2018, 20:18:21 CET schrieb Robert Krawitz:
> On Sun, 14 Jan 2018 14:03:22 -0500, J Albrecht wrote:
> >> On 14 Jan 2018, at 12:01, Pascal Obry <[email protected]> wrote:
> >> 
> >> Right, probably closer to Linux than Windows is. But yet, we have a
> >> single MacOS guy for the maintenance and he is not available actually
> >> to do the work. That illustrate my point :)
> > 
> > The point is not so pointy. There have actually been a number of people
> > who have offered to help in this regard. Yet, the offers were either
> > rejected or ignored. It seems that this is a 'closed club'.
> > 
> > Once again: I'd be quite happy to help package for MAC OS - even as
> > Parafin's third-rate 'apprentice' to assist in getting these things out
> > when he's not available. I've already successfully compiled 2.4.0 on my
> > Mac box. I've just not been able to produce a functional Disk Image. I
> > need assistance in that regard. Unlike Robert Krawitz suggests, I don't
> > feel that it's necessary to 'sign' the DMGs; the packages have been
> > provided unsigned for as long as they've been available. Nobody expects
> > them to be signed now! Furthermore, no current user expects them to be
> > available on Apple's bespoke store. People would just like them to be
> > available on the dt site ;-)
> Speaking from experience, I strongly suggest signing the package.
> Current users may be OK with the workaround, but growing the userbase
> will require pulling in new users who don't want to turn off the
> signing requirement (which is there for a reason, and even if it
> weren't, is something Apple strongly discourages and Mac users tend to
> listen to Apple).
> 
> When the signing requirement first came out (10.10, IIRC), we were
> deluged with compaints from users that Gutenprint wouldn't install on
> their Macs.  If you go this route, be prepared for complaints -- loud,
> vociferous ones.  And since Darktable has been getting publicity as a
> solution on Windows, you can expect more Macintosh users (not just
> curent ones) to want to get in on the act.  The "workaround" of
> turning off package signing won't fly with them, and it will suggest
> that it's bundled with malware. And it will also make it more
> difficult for you if third parties pick up Darktable, bundle it with
> ad/mal/junkware and distribute it themselves, since your instructions
> to turn off signature verification will make it easier for these
> operators.

Well, darktable is open source, so there wouldn't be anything we could do 
about that. If you want to bundle stuff you are in general free to.

[...]

> But I very strongly suggest, based on our experience with Gutenprint,
> that you get a certificate and sign the package.

The darktable team doesn't provide binary builds. It's individuals who do 
that. For Windows that has been me, for OSX it's parafin and Pascal is running 
the Ubuntu PPA. We are just helping out by hosting the files along with our 
Github release. Now, if one of those individuals decides to sign their package 
they are free to do so. More power to them. But I will make very sure that no 
money from darktable (the little that we have) will be spent to make Apple 
even richer, just so we can help them getting more users for their OS. I'd 
rather ignore a thousand complaining users.

Tobias

Attachment: signature.asc
Description: This is a digitally signed message part.

Reply via email to