From: Hannes Mehnert <hannes@mehnert.org>
To: caml-list@inria.fr
Subject: Re: [Caml-list] [rfc] deprecating opam 1.2.0
Date: Mon, 5 Jun 2017 09:29:18 +0200 [thread overview]
Message-ID: <5df01629-89e5-28cb-1c7f-15030db9e7b4@mehnert.org> (raw)
In-Reply-To: <CAGYXaSYzj3NG_t0_syktchFT_PqAeWnVoanDPqc61UAZq+804g@mail.gmail.com>
On 03/06/2017 16:48, Evgeny Roubinchtein wrote:
>> Is there anyone else that is still packaging 1.2.0? Please comment here
> if so, and we should move them away.
>
> FreeBSD ports still only has opam 1.2.0:
> https://www.freebsd.org/cgi/ports.cgi?query=opam&stype=all. DragonFly may
> be in the same boat, since, IIRC the ports collection is shared between the
> two. Also, what about pkgsrc?
To clarify, FreeBSD ports has opam 1.2.2 (since May 2015), not 1.2.0.
hannes
next prev parent reply other threads:[~2017-06-05 7:30 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
2017-06-05 7:29 ` Hannes Mehnert [this message]
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=5df01629-89e5-28cb-1c7f-15030db9e7b4@mehnert.org \
--to=hannes@mehnert.org \
--cc=caml-list@inria.fr \
/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