On Fri, Jul 6, 2012 at 6:05 PM, Hin-Tak Leung
<htl10@users.sourceforge.net> wrote:
--- On Fri, 6/7/12, Ismael Olea <ismael@olea.org> wrote:
From: Ismael Olea <ismael@olea.org>
Subject: Re: Yum repo
To: mono@lists.fedoraproject.org
Date: Friday, 6 July, 2012, 20:37
What are the next steps to a) getting the RPM spec files to do mono packaging and b) creating a yum repository suitable for EPEL to serve the mono packages?
Dave: EPEL current offers mono for RHEL 5 and 6
and all sources are available:
of course there are more mono packages but accessible using the same webapps
-- Ismael Olea
Besides Ismael's comment, the spec files, and other fedora specific patches can be got from git clone'ing
git://pkgs.fedoraproject.org/mono.git
(this should be obvious from the http pkg.fedoraproject link above)
. While it is true that RHEL and other redhat linux's shipped mono tends to be out-of-date - for obvious reasons, since you will need to rebuild everything that depends on mono, which is a lot! - fc18's - or rawhide's - is always up to date, and I have had no problems grabbing
an fc18 srpm and doing rpm --rebuild on fc17/fc16's, and occasionally get a few more pdated dependent packages when it does complains about dependencies.YMMV. |
Many other software packages offer alternative repositories for using newer builds on RHEL and CentOS - RabbitMQ and MongoDB, for example - so my hope is that there would be a similar repository for mono. I can understand that if other packages on the same system depend on mono, they would be affected, but my software is running alone within a virtual appliance so I have complete control over the software being installed. Thank you for pointing out the fc18 repository and if you've had luck with that, I will give that a go.
|
OTOH, if you do start to ship mono 2.10.8, or godforbid mono 2.11.2 for RHEL, you will have to provide the whole mono-dependent stack, which is not a small undertaking. Be warned...
|
It seems that the whole mono dependent stack already ships in the standard RHEL repos, as I can build mono 2.10.8 using this script, which pulls all it's dependencies from the standard repositories:
My software builds, runs, and tests as expected, so I believe 2.10.8 to work on CentOS 6, but I'd prefer not to require mono be built from source in order to deploy my software package. As such, I'm on the hunt for a repo, or, if I have to create my own, I want to follow the process to make it available for others as more users of the repo will improve the quality.
Thank you both for your guidance.