[opam-devel] opam-1.0.1?
Anil Madhavapeddy
anil at recoil.org
Mon Mar 18 16:12:47 GMT 2013
On 18 Mar 2013, at 11:09, Thomas Gazagnaire <thomas at ocamlpro.com> wrote:
>> The former won't be very nice when we fix the bug! We could just tell people to run trunk, yeah...
> we can still have a short transition period with ( os = "freebs" | os = "freebsd")
>
> An other option it to tell people to temporary edit their ~/.opam/<swith>/conf/con-ocaml.config to fix their os variable.
>
>>>> Thomas, should we issue a 1.0.1 point release with the fix, to make it easier to debug the other FreeBSD issues?
>>>
>>> Not sure it's worth running the release cycle again ...
>>
>> If there's nothing else in the queue immediately, it would be better not to let fixes linger in trunk... (but you might have other patches queued, hence this question)
>
> No, no urgent patches in the pipeline (I haven't pushed anything to opam since the release actually).
>
If there's nothing else, I think we should just cut a release... the problem is that it leaves people with a broken ~/.opam/<switch>/conf/con-ocaml.config, and a binary upgrade has to fix it up.
It seems prudent to prevent these broken configs as soon as possible, and release note the workaround...
-anil
(I haven't done the Deb packages yet, although of course this fix isn't material for Debian)
More information about the opam-devel
mailing list