caveat needs context

[dericed]

This caveat of mm

If using PREMIS DB, backup can be controlled via included plist file. This is configured to run daily backups at 2:00AM if activated. 

To have launchd start mediamicroservices/mm/mm now and restart at login:
  brew services start mediamicroservices/mm/mm

needs some context to say that is only relevant to systems running mm that are also hosting the database (ie not user computers).

[privatezero]

How is this wording? If using the PREMIS DB reporting feature of mm, backup can be controlled via included plist file. Backup only needs to be activated/configured on the DB host computer. Included plist file will run daily backups at 2:00AM if activated.

[retokromer]

Before that caveat, it gives following message on my test machine (no database linking, just using some of mm):

==> updateplist
Last 15 lines from /Users/test/Library/Logs/Homebrew/mm/post_install.01.updateplist:
2016-12-02 15:56:21 +0100

updateplist

Warning: The post-install step did not complete successfully
You can try again using `brew postinstall mediamicroservices/mm/mm`

which may be misinterpreted, I guess.

[privatezero]

Oh yeah! I can see how that could easily be misconstrued. Hmmm this is still something I am thinking about! Trying to find an unobtusive way to compensate for the way Homebrew handles MySQL updates...seems that there is some more tweaking to do!

[privatezero]

For now I will change the name of the script to 'updatingplist' so the on screen message will be less confusing.

[retokromer]

FYI: My remark comes from the experience made while advocating for open source solutions inside archives IRL.

[retokromer]

The full output for a new installation is:

[privatezero]

That certainly isn't how it is supposed to behave! Thanks for catching this!

[retokromer]

I have to add that, at least the part I’m using, works very fine, it’s «just» the messages that are a little… confusing for the λ user.

[retokromer]

Ping: any news on this?

[privatezero]

Not really - I haven't had problems with it on my end, but the script itself also isn't always behaving as intended.

From the beginning, this was a somewhat clumsy attempt to address Homebrew's annoying habit of locking MySQL down to local users only on every update.

I have been debating taking it out of the formula, and just documenting the issue and how to fix it in the mm documentation.

[retokromer]

Thank you! I have time until the 19^th of June, before I’ll teach… to ignore the warning ;-)

[retokromer]

I guess, this one can be closed.

cc @dericed @privatezero