From: "Richard W.M. Jones" <rich@annexia.org>
To: "Török Edwin" <edwin+ml-ocaml@etorok.net>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Anybody interested in creating binary RPMs for each official release of the compiler?
Date: Tue, 25 Mar 2014 08:41:17 +0000 [thread overview]
Message-ID: <20140325084117.GC21875@annexia.org> (raw)
In-Reply-To: <5330B457.6010309@etorok.net>
On Tue, Mar 25, 2014 at 12:40:23AM +0200, Török Edwin wrote:
> Since ocaml4* doesn't exist in RHEL/CentOS, then it doesn't conflict.
> Also it seems gcc uses the same convention, at least I see a gcc44 and a gcc package, so as long as
> ocaml4* wouldn't install conflicting binaries it might work, wouldn't it?
You can bend the rules and do stuff which obviously conflicts with the
intended policy even if it doesn't strictly break it, but I'm not
going to be a part of that when you can use an external repo instead.
You'd still have to rename the executables (eg. /usr/bin/ocamlopt4),
or you'll be causing a support headache for people who pay for RHEL
and install EPEL and then install conflicting packages without really
understanding what they are doing.
Rich.
--
Richard Jones
Red Hat
next prev parent reply other threads:[~2014-03-25 8:41 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 [this message]
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=20140325084117.GC21875@annexia.org \
--to=rich@annexia.org \
--cc=caml-list@inria.fr \
--cc=edwin+ml-ocaml@etorok.net \
/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).