[Mono-dev] Distribute Parallel Mono Environment?

Rick Tillery rtillerywork at gmail.com
Tue Aug 23 20:54:42 UTC 2016

Wow!  That looks like a lot of work.  I'll need to take a closer look and
see how it works.  On first glance, it looks like you're building mono (not
using pre-built binaries), but this looks quite different from my build
process.  It seems like you simply set the prefix, which would be a lot
simpler than what I did.  Of course, I worried about whether the guide I
used to build the parallel environment
would work at all, since it references version 1.x.  It would be nice if
there were a simpler way put into place since then :-)

Our app will install on customers'/users' machines.  Our concern, in
addition to an updated mono on the repo that breaks our app at install time
(which is what we hit last month), is that these machines may have mono
updated in conjunction with another installed app, and that breaks our app.


On Tue, Aug 23, 2016 at 3:20 PM, Timotheus Pokorra <
timotheus.pokorra at solidcharity.com> wrote:

> Hello Rick,
> Have a look at my mono-opt.spec file:
> https://github.com/tpokorra/lbs-mono/tree/master/mono-opt
> This rpm installs mono to /opt/mono.
> Is your application installed on your own servers, or on machines of
> customers/users?
> If it is on machines that you control, what you need is not
> necessarily mono in a parallel environment, because you only need Mono
> once.
> 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,
>   Timotheus
> 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,
> > Rick
> >
> > _______________________________________________
> > Mono-devel-list mailing list
> > Mono-devel-list at lists.dot.net
> > http://lists.dot.net/mailman/listinfo/mono-devel-list
> >
> --
> Kontaktdaten:
> in Plauen: 03741 7424995
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.dot.net/pipermail/mono-devel-list/attachments/20160823/3c74da86/attachment.html>

More information about the Mono-devel-list mailing list