View Single Post
Old 12-06-2020, 06:15 PM   #4
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 8,859
Karma: 6120478
Join Date: Nov 2009
Device: many
That seems okay to me as long as they point to the latest 1.4.3 txz version and it matches exactly our shasum -a 256 output.

I personally just do not use Homebrew for much of anything as no matter how I try, it ends up installing things under /usr/local that end up being found and used in builds before the versions I personally build to run on macOS specific 10.12 versions of macOS.

If it installed literally *everything* in /opt/cask/ guaranteed and never ever touched /usr/local I would be much much happier. I tried their published way of trying that but inevitably one or more packages always ended up in usr local.

Kevin


Quote:
Originally Posted by DiapDealer View Post
@KevinH : You're the Mac expert here, so I don't want to give any bad advice. But I just learned today that the Homebrew version of Sigil literally uses the txz file from our releases for its Sigil installation. And they're staying current with our releases. Do you think it might be worth mentioning a Homebrew Sigil install to some Mac users as an alternative method? It compares our sha256 checksum as part of its process.
KevinH is offline   Reply With Quote