Re: Update Hombrew install instructions on the web site

Thomas Leonard <[email protected]>
Newsgroups gmane.comp.file-systems.zero-install.devel
Message-ID <CAG4opy8j73VBf+fYvSC=KUdZma1UuME_JTkO3YNVDb3VqLfL-Q@mail.gmail.com>
On 2 August 2015 at 17:23, Anders F Björklund <[email protected]> wrote:
> Thomas Leonard wrote:
>
>>> I made a test, and it seems that you still need to "init" the opamroot
>>> and it would need to download the "urls.txt" and the "index.tar.gz" ?
>>
>> If you've added the local clone of the repository, you can probably
>> remove the default one ("opam remote remove default"). That should
>> stop it trying to fetch any updates.
>
> Thanks for the hint about the opam-repository, makes it easy to get a
> snapshot of what opam modules were in fashion at the time of release...
>
> Actually I meant the case where I constructed an *empty* opamroot,
> just for the build. I think adding the repo there only makes it worse ?
>
> ==> opam init --no-setup
> [WARNING] /tmp/zero-install20150802-430-1707xb1/0install-2.8/opamroot exists
>            and is not empty
> Proceed ? [Y/n] y
>
> I pre-populated the "archives", which was why it was not empty.
>
>>> And I don't really want to go through the hassle of having to maintain
>>> all the dependencies, and update them if there's new versions etc etc.
>>
>> Yes, this does seem like an annoying requirement.
>
> But seems necessary, like in case of Lwt below ? Should be some way
> to "pin" opam to use the bundled libraries, if it can't stay offline.

If you delete from opam-repository all the versions you're not using,
it won't have any choice :-)

Or, you could add some exact version constraints to 0install's opam file.

> I know that I did this for the release, since the "sha" module didn't
> work with the older SDK (bug filed). Seems missing on Fedora as well ?
>
> Anyway, it happily ignored my archives and just went with the latest:
>
> ==> opam install yojson xmlm ounit react lwt extlib ocurl lablgtk sha
> The following actions will be performed:
>    ∗  install ocamlfind   1.5.5                                [required
> by xmlm, react, ocurl, etc.]
>    ∗  install camlp4      4.02+system                          [required
> by lablgtk, extlib, lwt]
>    ∗  install xmlm        1.2.0
>    ∗  install sha         1.9
>    ∗  install react       1.2.0
>    ∗  install ppx_tools   0.99.2                               [required
> by lwt]
>    ∗  install ounit       2.0.0
>    ∗  install easy-format 1.0.2                                [required
> by yojson]
>    ∗  install cppo        1.1.2                                [required
> by yojson]
>    ∗  install lablgtk     2.18.3
>    ∗  install extlib      1.6.1
>    ∗  install biniou      1.0.9                                [required
> by yojson]
>    ∗  install lwt         2.5.0
>    ∗  install yojson      1.2.1
>    ∗  install ocurl       0.7.5
> ===== ∗  15 =====
>
> Will see if I can't get it to install the ones that I provided instead.

You can specify versions like this:

opam install 'lwt=2.5.0'

But it might be easier to 'opam install 0install' and grab the binary
it produces.

> Preferrably I would have it just use the archives that I provided, but
> it seems that this is not the way that OPAM is supposed to be working.
>
>>> It ended up failing on some unicode issue, as it always seems to do...
>>> Same old string vs. bytes failure that we know and love from python3.
>>> Not sure if that's just a feature from ocaml 4.02.3 and opam 1.2.2 or not ?
>>> Seemed to work the last time I tried it. And what was with lwt <= 2.4.6 ?
>>
>> Lwt 2.4.7 changed a type from string to bytes I think, which broke the
>> build when using -safe-string:
>>
>>    https://github.com/ocaml/opam-repository/pull/3456
>
> Right, this was the error that I was seeing with the brew ocaml.
> Didn't see it for my earlier build, when using an older compiler.
>
> But if it had just used Lwt 2.4.6, then things would have worked ?
> Seems like another reason to note down the versions of each then.
>
>> Was fixed in the git version of 0install in Jan 2015. I should
>> probably make a new release at some point, but for now using the older
>> Lwt works. Or, you can apply this patch:
>>
>> https://github.com/0install/0install/commit/5b32a90ed160c3523a46addd747a9c45a49f56ec
>
> Ah, thank you. That makes much more sense, patching for newer then.
> Saw that you made the 2.9 release, but nice to have both of them...
>
> There is also a --HEAD version, that will use the 0install.git HEAD.
> Made that one use the locally installed (latest) opam modules too.
>
>
> Will push them soon, it seems to be working OK with "linuxbrew" too.
>
> Though I left obus out of the packaging, so it won't have PackageKit.
>
> /Anders
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Zero-install-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/zero-install-devel



-- 
Dr Thomas Leonard        http://roscidus.com/blog/
GPG: DA98 25AE CAD0 8975 7CDA  BD8E 0713 3F96 CA74 D8BA

------------------------------------------------------------------------------
_______________________________________________
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.