[opam-devel] [ocaml-platform] opam 1.1.1 to be released shortly

Vsevolod Stakhov vs374 at cam.ac.uk
Sat Jan 11 23:15:31 GMT 2014

On 11.01.2014 22:59, Anil Madhavapeddy wrote:
> [dropping platform@ from CC]
> On 10 Jan 2014, at 17:44, Roberto Di Cosmo <roberto at dicosmo.org> wrote:
>> - check the patch added by Ralf in the latest version of the
>>    Debian aspcud package to ensure backwards compatibility of
>>    the optimization criteria supported by the latest aspcud
>>    with the legacy criteria supported by the other solvers...
>>    this basically boils down to adding a few lines to the
>>    aspcud bash shell to use a short sed file and convert the
>>    old criteria in the new language supported by the latest
>>    aspcud... you'll find attached the modified aspcud and the
>>    sed file from the Debian package
> This makes maintaining the port on other platforms really tough,
> since we have to keep looking at both upstream and the Debian
> packages.  Are these patches not suitable to be fed upstream into
> one patched tarball that could be installed by the various package
> managers?

I agree, as both debian packages and FreeBSD ports are aimed to have OS 
specific patches only in the tree. In a very special cases when upstream 
authors are unresponsive to critical bugs it is worth to enforce generic 
patches to be included, however, it seems that aspcud authors are rather 
active and it is worth to ask them first. Actually, my libc++ specific 
patch is from the same source: aspcud uses non-standard conventions of 
libstdc++ which is definitely not a good decision (for example, OS X 
uses clang as well).

Vsevolod Stakhov

More information about the opam-devel mailing list