Re: Update Hombrew install instructions on the web site

Anders F Björklund <[email protected]>
Newsgroups gmane.comp.file-systems.zero-install.devel
Message-ID <[email protected]>
Björn Pollex wrote:
>> I tried the homebrew instructions on OS X Yosemite, and there
>> doesn't seem to be anything *majorly* wrong with it afaict... ?
>>
>> $ brew install gettext pkg-config gnupg gtk+ ocaml opam
>>
>> $ opam install yojson xmlm ounit react lwt extlib ssl ocurl lablgtk
>>
> These are not the Homebrew installation instructions, these are the 
> Source installation instructions. The current web site has a separate 
> section further down titled *Homebrew installation*, which contains 
> instructions that donÂ’t work anymore because the recipe for 0install 
> has been removed from homebrew, as you have pointed out previously. 
> Cask <http://caskroom.io> is a command extension for Homebrew that can 
> be used to install Mac OS X native packages. The main repo for casks 
> is separate from homebrew.

Ah, you are correct. Sadly it was rejected, so it needs to either be 
cherry-picked or put into a separate repository or something - neither 
of which helps much with providing a binary bottle I guess. It's an 
option, but then "someone else" needs to provide those (github/bintray).

I wrote a lot of different installation instructions, and seem to be 
confusing even myself. :-)

Apparently homebrew-cask just calls "sudo installer -pkg *.pkg -target 
/", which is pretty normal and the same command that we describe - so 
wonder what went wrong. You could check if /usr/local/bin/gpg and 
/opt/gtk/bin/gtk-demo ended up in the usual places, maybe try them 
separately ?

Anyway, this Cask thing seems to rather different from Homebrew - more 
of a fork, really.

> I donÂ’t know why the GTK+ dependency is missing. Cask only executes 
> the packager installer, so maybe that installer doesnÂ’t install the 
> dependency?

The GnuPG and PyGTK packages are separate, but the ZeroInstall package 
is supposed to download them and install them unless you "uncheck" the 
optional dependencies - theory being that you already installed them, 
the last time around. Mostly to cut down on the download size, but also 
for licensing.

But http://macpkg.sourceforge.net is getting a bit old, and I plan on 
retiring it. The universal packages are built for Mac OS X 10.6, and 
needs updating. And then comes GnuPG 2 and GTK+ 3 mudding the waters 
further. Probably easier to just do a packaging for 0install, and ship 
it under the GPL instead ?

> As a test IÂ’ve uninstalled 0install and downloaded the Bundle from the 
> web site <http://0install.net/install-osx.html>. When I try to run it 
> Mac OS (IÂ’m on 10.10.4) says it is damaged and canÂ’t be executed. I 
> donÂ’t know why it works with Cask, which is essentially doing the same 
> thing. IÂ’d love to help resolve this, so please let me know what I can 
> do. IÂ’m currently learning 0install and will probably come back with 
> more questions over the next few weeks.

I'm thinking that it needs a new build only for 10.9 and later, which 
also enables ditching 32-bit. There's always the option of going back to 
plain old tarballs. Just that there quite a lot of them, for everything ?

We have the "Darwin-x86_64" ones on 
http://0install.net/tools/0install.xml ("generic binaries"), but then 
you need to provide gnupg/gtk+. We tried (and failed) with 
fink/port/brew, and pkg isn't too much fun...

--anders

------------------------------------------------------------------------------
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/

_______________________________________________
Zero-install-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/zero-install-devel
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.