Re: Yum repo

[Hin-Tak Leung]

--- On Mon, 9/7/12, Dave Curylo <curylod(a)asme.org&gt; wrote:

From: Dave Curylo <curylod(a)asme.org&gt;
Subject: Re: Yum repo
To: htl10(a)users.sourceforge.net
Cc: "mono" <mono(a)lists.fedoraproject.org&gt;
Date: Monday, 9 July, 2012, 12:54


On Mon, Jul 9, 2012 at 1:28 AM, Hin-Tak Leung <htl10(a)users.sourceforge.net&gt; wrote:



You seems to not understand what I was saying. I am not talking about what latest mono
depends on, but what depends on mono. 



I get what you're saying. As I said before, I 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.
My concerns here are merely with the deployment of the mono 2.10 framework for use by my
software. I'm not interested in replacing the system level libraries that provide RHEL
and CentOS with its enterprise grade stability - just a framework that sits on top of that
stable system.  It's a matter of being able to choose the software framework(s) I wish
to run on the system that I control.


> From this discussion, it sounds like EPEL is the wrong place for
> shipping a recent version of mono given the stated goal of "EPEL packages are usually
> based on their Fedora counterparts and will never conflict with or replace packages in the
> base Enterprise Linux distributions."  If you have a recommendation of a repo that
> ships a recent version or would be willing to include one if there was a package
> maintainer, please let me know. 

Thanks again for your help.
Whichever you choose/approach is, I think there is some maintainence work-load involved if
you want to keep both the system up to date as well as having the latest mono. If you
choose to do rpm --rebuild a rawhide rpm to replace those in a earlier distro (be is EPEL
or current fedora), you run the risk of eventually having to resolve conflicts; it may be
simplier to ship your virtual appliance as a completely stock/up-to-date EPEL/fedora
without any mono related pieces, and have an up-to-date mono installed under /usr/local
and outside of the package management system. (and you would want to ship as minimal a
system as possible in either case).