caml-list - the Caml user's mailing list
 help / Atom feed
From: SF Markus Elfring <elfring@users.sourceforge.net>
To: Kenneth Adam Miller <kennethadammiller@gmail.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Opam improvement request
Date: Tue, 25 Dec 2018 10:00:58 +0100
Message-ID: <a24bff44-bab0-9db3-72f6-05c4b367c652@users.sourceforge.net> (raw)
In-Reply-To: <CAK7rcp-JHkjq8fEaz=KdM+hbCwC_TLhu6cSXmWA+uzsjiSLsUg@mail.gmail.com>

> I don't want to manage specification files, …

I propose to take another look around consequences for such a wish.


> And that's because I don't care if I have even 20 times as much space consumed
> by opam because opam is keeping old states.

Are there any circumstances under which you would start to care
(or become concerned about corresponding storage allocation challenges)?


> All I'm saying is I don't want to have some dependency version mismatch
> cause the current system to become inoperable, …

I can generally follow such a desire to some degree.
But safe dependency management can also require to express expectations
for system properties in precise ways, can't it?

Would you like to fiddle with application binary interfaces?


> Again, opam packages change all the time, and if you don't regularly stay
> up to date, it's really easy to get downwind of drastic changes;
> leaping many versions for a given package can trigger the kinds of
> unexpected breaks that I'm talking about.

There are more challenges to consider from usual software evolution.


> It makes sense to me to think of opam package installs as being in a kind of
> git staging area, where I can consider them tentatively and test it against
> a particular package, but easily and quickly revert back to other built packages

You might stumble on target conflicts which will make it harder to find
and agree on a solution.


> (without needing to rebuild something again unnecessarily) that I know are working.
It can take a while until it is noticed that something is finally not working
as expected, can't it?

Regards,
Markus

-- 
Caml-list mailing list.  Subscription management and archives:
https://sympa.inria.fr/sympa/arc/caml-list https://inbox.ocaml.org/caml-list
Forum: https://discuss.ocaml.org/
Bug reports: http://caml.inria.fr/bin/caml-bugs

  reply index

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-24 21:11 Kenneth Adam Miller
2018-12-25  9:01 ` SF Markus Elfring [this message]
2018-12-25  9:50 ` katherine
2018-12-25 17:43   ` Kenneth Adam Miller
2019-01-03 16:46 ` Louis Gesbert

Reply instructions:

You may reply publically 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=a24bff44-bab0-9db3-72f6-05c4b367c652@users.sourceforge.net \
    --to=elfring@users.sourceforge.net \
    --cc=caml-list@inria.fr \
    --cc=kennethadammiller@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

caml-list - the Caml user's mailing list

Archives are clonable: git clone --mirror https://inbox.ocaml.org/caml-list

AGPL code for this site: git clone https://public-inbox.org/ public-inbox