From: Jeremie Dimino <jdimino@janestreet.com>
To: "ocaml-core@googlegroups.com" <ocaml-core@googlegroups.com>
Cc: "caml-list@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] Package renamings for sexplib, bin_prot and a few other camlp4 syntax extensions
Date: Tue, 26 Jan 2016 17:17:10 +0000 [thread overview]
Message-ID: <CANhEzE7NV5XQp0iSXXFz147OzTVnq7CujcSoENsiBdNH+eVEpA@mail.gmail.com> (raw)
In-Reply-To: <CALdWJ+zCqZws+hVJKTGcx0KN0RoFSLMOb2==GDjRQCf2YYgGfw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 973 bytes --]
On Tue, Jan 26, 2016 at 4:56 PM, Ivan Gotovchits <ivg@ieee.org> wrote:
> > 3. release project.0.3.1, keeping project.0.3 unchanged
>
> The problem is that `project.0.3` will be broken for ever, as well as all
> dependencies that depend on this particular version.
>
> Maybe there is actually some misunderstanding, and we're talking about
> different things. Just to clarify, are you going to go
> through opam-repository and update all archives of old libraries (e.g.
> sexplib.7.0.5, sexplib.108.00, ...) and remove `<library>.syntax`
> findlib library from it? This is what I'm afraid of. And this is what I
> name "retroactively".
> As according to the PR there is nothing like this. If all old archives
> will be still available, then it is perfectly fine.
>
Indeed, I misunderstood your original question. Sorry about that.
We definitely won't touch the archive of any released package. I agree that
would be disastrous...
--
Jeremie
[-- Attachment #2: Type: text/html, Size: 1819 bytes --]
next prev parent reply other threads:[~2016-01-26 17:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-26 10:44 Jeremie Dimino
2016-01-26 13:57 ` Ivan Gotovchits
2016-01-26 14:50 ` Jeremie Dimino
2016-01-26 15:15 ` Ivan Gotovchits
2016-01-26 16:15 ` Jeremie Dimino
2016-01-26 16:56 ` Ivan Gotovchits
2016-01-26 17:17 ` Jeremie Dimino [this message]
2016-02-03 10:37 ` Jeremie Dimino
2016-02-03 19:20 ` ygrek
2016-02-05 9:36 ` Jeremie Dimino
2016-03-09 15:56 ` Junsong Li
2016-03-09 16:06 ` Jeremie Dimino
2016-03-09 16:23 ` Junsong Li
2016-03-09 17:16 ` Ivan Gotovchits
2016-03-09 17:31 ` Junsong Li
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=CANhEzE7NV5XQp0iSXXFz147OzTVnq7CujcSoENsiBdNH+eVEpA@mail.gmail.com \
--to=jdimino@janestreet.com \
--cc=caml-list@inria.fr \
--cc=ocaml-core@googlegroups.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).