https://bugs.documentfoundation.org/show_bug.cgi?id=166677

Patrick (volunteer) <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[email protected]

--- Comment #9 from Patrick (volunteer) <[email protected]> ---
(In reply to Buovjaga from comment #7)
> I know there is no such executable, it was a pseudo-command to give a point
> of reference. It was the best I could do in a hurry as a non-macOS user.

Sorry I didn't make it clear, but I cc'd you and cloph because it was obvious
to me that this bug was another case of the recurring download problem for Mac
Intel users since LibreOffice switched the default Mac chip earlier this year.

Maybe this isn't on TDF staff's radar, but it is clear to me that a steady
stream of Mac Intel users now download the installer from the LibreOffice site
like they always have and, after they install it, they are dead in the water.
That can't be helping TDF donations.

This wasn't much of a problem before the switch since Apple gave Mac Silicon
users a smooth way to make Mac Intel applications run. But Mac Intel users have
no such alternative and are left wondering why the process they have always
used to download LibreOffice has now overwritten their working LibreOffice with
an unrunnable one. And worse, redownloading the older version they were using
doesn't work either.

I don't think the new support load that this switch caused is going to go away
on its own anytime soon. I admit that I still don't understand why TDF staff
only ships a universal installer in the Mac App Store and not the LibreOffice
download page but the current combination of non-universal installer and Mac
Silicon as the default chip have created frustration and confusion for Mac
Intel users.

Whether you like it or not, you and cloph are the owners of this problem.
Shipping a universal installer would eliminate this problem entirely. But if
TDF staff are against that, then both of you should at least bear some
responsibility for handling the support load that your approach has created.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to