[Caml-list] Re: AW: GODI is shutting down

[Sylvain Le Gall <sylvain@le-gall.net>]

On 25-07-2013, Leo White <lpw25@cam.ac.uk> wrote:
>>> However, the main problem (the one I wanted to point out) still
>>> remains: every time you want to fix a constraint you have to change
>>> your _oasis, modify the package tarball, and make a new release --
>>> which means you can never fix constraints on already released
>>> packages. But I guess in this case, it's fine if the _oasis and OPAM
>>> files are not in sync.
>>>
>>
>> We don't share the same POV here. If a constraints is bad it should be
>> fixe in the upstream version. A quick fix could be to patch it in OPAM,
>> but if a constraint is bad with OPAM, Debian packagers will have to do
>> the same kind of fix. So we should make it upsteam, not keep the fix in
>> OPAM.
>>
>
> I think that Thomas' point was that if you extract the dependecies
> directly from an _oasis file within the package then you can only fix
> dependencies in future versions of the package.
>
> So, if foo-0.5.6 has a bad dependency (extracted from the _oasis file
> within foo-0.5.6) making the fix upstream will only help foo-0.5.7
> onwards: foo-0.5.6 will still be in the repository and its dependencies
> will still be incorrect.
>
> I am sure he agress that fixes should be passed upstream, but we also
> need to be able to correct dependencies in existing packages.
>

Getting out of sync for older packages seems fine to me! The system
should allow override and that should be ok. 

At least we agree on this point!

Cheers,
Sylvain Le Gall
-- 
Website:     http://sylvain.le-gall.net/
OCaml forge: http://forge.ocamlcore.org
OCaml blogs: http://planet.ocaml.org