[Mono-dev] Distribute Parallel Mono Environment?
timotheus.pokorra at solidcharity.com
Tue Aug 23 20:20:15 UTC 2016
Have a look at my mono-opt.spec file:
This rpm installs mono to /opt/mono.
Is your application installed on your own servers, or on machines of
If it is on machines that you control, what you need is not
necessarily mono in a parallel environment, because you only need Mono
I guess if you have your own build packages, you won't need the
Xamarin Repo. So you could just use the src rpms from Xamarin (see
http://download.mono-project.com/repo/centos/m/mono-core/, look for
src.rpm) at a point where you want it, and create your own repo with
that version, and only install from your own repo.
Or another alternative, you could still use the Xamarin repo, but
disable it after installation. (enabled=0 in the /etc/yum.repos.d/
xamarin repo file). Only when you have verified on a test machine,
that a newer version from the Xamarin repo would not break your
application, you enable the repo file (enabled=1), and upgrade.
hope this helps,
On 23 August 2016 at 22:10, Rick Tillery <rtillerywork at gmail.com> wrote:
> We have an application that can be (and has been) broken by a mono update to
> the repo. It seems that using a parallel mono environment is the most
> reasonable way to ensure we can tie our app to a specific mono version
> (until we can validate an update). ("mkbundle --static..." appears to have
> been deprecated.) So, what is the recommended way to distribute a parallel
> mono environment? We won't be building on the target machines, so it's
> creating our own package, right? Is there a sample of such a spec file? If
> not, where would the spec file for mono itself be located (specifically for
> CentOS/RHEL)? I can't find it in the mono repo.
> Thanks for your help,
> Mono-devel-list mailing list
> Mono-devel-list at lists.dot.net
in Plauen: 03741 7424995
More information about the Mono-devel-list