From: David Allsopp <dra-news@metastack.com>
To: Evgeny Roubinchtein <zhenya1007@gmail.com>,
Anil Madhavapeddy <anil@recoil.org>
Cc: caml users <caml-list@inria.fr>, opam-devel <opam-devel@lists.ocaml.org>
Subject: RE: [Caml-list] [rfc] deprecating opam 1.2.0
Date: Sat, 3 Jun 2017 15:04:06 +0000 [thread overview]
Message-ID: <E51C5B015DBD1348A1D85763337FB6D90135DB0C88@Remus.metastack.local> (raw)
In-Reply-To: <CAGYXaSYzj3NG_t0_syktchFT_PqAeWnVoanDPqc61UAZq+804g@mail.gmail.com>
Evgeny Roubinchtein wrote:
> One annoyance is that well-behaved ports are only supposed to
> access network during the "fetch" stage, so one would need to
> replicate in the FreeBSD port's Makefile the targets from the
> opam source tree that download various things during opam's
> build (I think it's mostly things in src_ext). That isn't an
> insurmountable obstacle, by any means, but just a bit of work
> that needs to be done.
See https://github.com/ocaml/opam/pull/2956/commits/13fdc7e4707d16748b9994cd6299bc259b4dd6da (which is in the process of being merged) and https://github.com/dra27/opam/commit/0f22342962d18aff4da4da0f206fb3a0aa278742 (which will head in a similar direction soon).
13fdc7e gives you make -C src_ext cache-archives which will download all the src_ext tarballs to src_ext/archives
If you then explicitly download the ocaml sources tarball to src_ext/archives/, then 0f2234 ensures that make cold uses it
HTH,
David
next prev parent reply other threads:[~2017-06-03 15:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-02 10:09 Anil Madhavapeddy
2017-06-02 12:16 ` Hendrik Boom
2017-06-02 13:31 ` Anil Madhavapeddy
2017-06-03 14:48 ` Evgeny Roubinchtein
2017-06-03 15:04 ` David Allsopp [this message]
2017-06-05 7:29 ` Hannes Mehnert
2017-06-11 18:27 ` Anil Madhavapeddy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E51C5B015DBD1348A1D85763337FB6D90135DB0C88@Remus.metastack.local \
--to=dra-news@metastack.com \
--cc=anil@recoil.org \
--cc=caml-list@inria.fr \
--cc=opam-devel@lists.ocaml.org \
--cc=zhenya1007@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).