caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Florian Weimer <fw@deneb.enyo.de>
To: caml-list@inria.fr
Cc: Francois Berenger <berenger@riken.jp>
Subject: Re: [Caml-list] Anybody interested in creating binary RPMs for each official release of the compiler?
Date: Sat, 29 Mar 2014 22:08:36 +0100	[thread overview]
Message-ID: <877g7c3e7f.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <20140324110207.GA18751@annexia.org> (Richard W. M. Jones's message of "Mon, 24 Mar 2014 11:02:07 +0000")

* Richard W. M. Jones:

>> But ideally, any rpm-based distro should have access
>> to the recent OCaml compilers, I fell (or I am just dreaming).
>
> We have to stick with the original OCaml compiler on RHEL releases
> because of binary compatibility.  Also EPEL policy doesn't allow us to
> ship an upgrading OCaml compiler in EPEL, since we can't replace
> packages from the original RHEL.

Technically, you could ship a Software Collection (RPM packages which
install under /opt and come with metadata to support integration with
sclutils).  Does EPEL policy allow that?

  parent reply	other threads:[~2014-03-29 21:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-24  1:41 Francois Berenger
2014-03-24  8:33 ` Richard W.M. Jones
     [not found]   ` <532FF7C6.8010608@riken.jp>
     [not found]     ` <20140324110120.GM3162@annexia.org>
2014-03-24 11:02       ` Richard W.M. Jones
2014-03-24 18:36         ` Török Edwin
2014-03-24 22:18           ` Richard W.M. Jones
     [not found]             ` <5330B457.6010309@etorok.net>
2014-03-25  8:41               ` Richard W.M. Jones
2014-03-29 21:08         ` Florian Weimer [this message]
2014-03-31  1:22           ` Francois Berenger
2014-03-31  6:02             ` Stéphane Glondu
2014-03-26  1:13       ` Francois Berenger
2014-03-26 16:57 ` Fabrice Le Fessant
2014-03-27  2:32   ` Francois Berenger

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=877g7c3e7f.fsf@mid.deneb.enyo.de \
    --to=fw@deneb.enyo.de \
    --cc=berenger@riken.jp \
    --cc=caml-list@inria.fr \
    /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).