From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@sympa.inria.fr Delivered-To: caml-list@sympa.inria.fr Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by sympa.inria.fr (Postfix) with ESMTPS id C3B077F890 for ; Mon, 24 Mar 2014 23:18:46 +0100 (CET) Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of rich@annexia.org) identity=pra; client-ip=80.68.91.176; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="rich@annexia.org"; x-sender="rich@annexia.org"; x-conformance=sidf_compatible Received-SPF: Pass (mail2-smtp-roc.national.inria.fr: domain of rich@annexia.org designates 80.68.91.176 as permitted sender) identity=mailfrom; client-ip=80.68.91.176; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="rich@annexia.org"; x-sender="rich@annexia.org"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of postmaster@furbychan.cocan.org) identity=helo; client-ip=80.68.91.176; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="rich@annexia.org"; x-sender="postmaster@furbychan.cocan.org"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AkkDAOuuMFNQRFuwl2dsb2JhbABZg0HDQgMCgSMWDgEBAQEBCBYHPIIlAQEBBAwmAUYQCxgJEwcLDwUoIYgQAQjPHheGAog2QgeDJIEUBJhJgTOSboE+PYEu X-IPAS-Result: AkkDAOuuMFNQRFuwl2dsb2JhbABZg0HDQgMCgSMWDgEBAQEBCBYHPIIlAQEBBAwmAUYQCxgJEwcLDwUoIYgQAQjPHheGAog2QgeDJIEUBJhJgTOSboE+PYEu X-IronPort-AV: E=Sophos;i="4.97,723,1389740400"; d="scan'208";a="64529016" Received: from furbychan.cocan.org ([80.68.91.176]) by mail2-smtp-roc.national.inria.fr with ESMTP/TLS/DHE-RSA-AES128-SHA; 24 Mar 2014 23:18:27 +0100 Received: from rich by furbychan.cocan.org with local (Exim 4.80) (envelope-from ) id 1WSDCK-00065s-4e; Mon, 24 Mar 2014 22:18:24 +0000 Date: Mon, 24 Mar 2014 22:18:24 +0000 From: "Richard W.M. Jones" To: =?iso-8859-1?B?VPZy9ms=?= Edwin Cc: caml-list@inria.fr Message-ID: <20140324221824.GF10374@annexia.org> References: <532F8D40.4030007@riken.jp> <20140324083301.GE10374@annexia.org> <532FF7C6.8010608@riken.jp> <20140324110120.GM3162@annexia.org> <20140324110207.GA18751@annexia.org> <53307B19.9090907@etorok.net> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <53307B19.9090907@etorok.net> User-Agent: Mutt/1.5.21 (2010-09-15) Subject: Re: [Caml-list] Anybody interested in creating binary RPMs for each official release of the compiler? On Mon, Mar 24, 2014 at 08:36:09PM +0200, Török Edwin wrote: > On 03/24/2014 01:02 PM, Richard W.M. Jones wrote: > > 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. > > What if you use a different package name? > Apparently there are some RPMs for CentOS6 called ocaml4-*: > http://pkgs.org/search/?query=ocaml4&type=smart Those are packages outside EPEL, which means that a CentOS user would have to add another repo, or deal with dependencies themselves (yuck). But yes, you can create a repo which contains whatever packages you want, if you can persuade people to add your repo. All it needs is a webserver, or you can use COPR to host it (like PPAs for EPEL). The actual policy is here: https://fedoraproject.org/wiki/EPEL/GuidelinesAndPolicies#Policy_for_Conflicting_Packages Rich. -- Richard Jones Red Hat