[opam-devel] depopt constraints not respected

[Roberto Di Cosmo]

I see your point, and I agree that we should work out together a simple and
compact solution.

But to be safe we need a well defined semantics, and it's better to have some
time to work it out and specify it formally before coding, to avoid further
surprises later on.

Adding the conflicts line has the advantage of fixing the issue at hand and
keeping the flexibility of the depopts, with a marginal cost, in the meanwhile.

--
Roberto



On Sat, Apr 05, 2014 at 05:35:48PM +0200, Daniel Bünzli wrote:
> 
> 
> Le samedi, 5 avril 2014 à 17:15, Roberto Di Cosmo a écrit :
> 
> > - we have many opam users around that are potentially being
> > hit by this issue right away: is it easier to add a single
> > line to a few packages in the repository, or to change opam,
> > test-it, roll it out and ask everybody to use the git dev
> > version?
> 
> Sure, but in the long term I'd really like opam doing that. The current situation goes against the DRY principle and common sense.  
> 
> Daniel
> 
>