From: "Richard W.M. Jones" <rich@annexia.org>
To: Francois Berenger <berenger@riken.jp>, caml-list@inria.fr
Subject: Re: [Caml-list] Anybody interested in creating binary RPMs for each official release of the compiler?
Date: Mon, 24 Mar 2014 11:02:07 +0000 [thread overview]
Message-ID: <20140324110207.GA18751@annexia.org> (raw)
In-Reply-To: <20140324110120.GM3162@annexia.org>
On Mon, Mar 24, 2014 at 06:15:50PM +0900, Francois Berenger wrote:
> On 03/24/2014 05:33 PM, Richard W.M. Jones wrote:
> >On Mon, Mar 24, 2014 at 10:41:20AM +0900, Francois Berenger wrote:
> >>I'm always annoyed when I have to wait ~20mn to install OCaml on a machine.
> >>
> >>Nowadays, thanks to OPAM, I think only a compiler is needed to
> >>bootstrap quickly an OCaml environment for developers.
> >
> >Binary RPMs for which distro?
>
> I am personally interested into:
>
> CentOS release 6.4 (Final)
> CentOS release 6.5 (Final)
>
> 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.
> I don't know anything yet about RPM packaging.
Start with the RPM spec file from Fedora Rawhide:
http://pkgs.fedoraproject.org/cgit/ocaml.git/tree/
Use fedpkg to build an SRPM from that.
> I don't know how the src RPMs are portable across
> distros and if they allow easily to create binary RPMs.
It's very difficult to have a binary RPM that would work on any
distro. I would say practically impossible.
However you could conceivably have a source RPM that can be rebuilt on
several RPM-based distros, using rpmbuild --rebuild ocaml-XXX.src.rpm.
It would have lots of %-conditionals ...
Rich.
--
Richard Jones
Red Hat
next prev parent reply other threads:[~2014-03-24 11:02 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 [this message]
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
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=20140324110207.GA18751@annexia.org \
--to=rich@annexia.org \
--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).