We have an application that can be (and has been) broken by a mono update to the repo <https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fbugzilla.xamarin.com%2fshow_bug.cgi%3fid%3d41953&data=01%7c01%7cRob.DeRosa%40microsoft.com%7cecb2fa4004c149ab6b1208d3c79c3280%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=%2fSXJZaTA0axCLkJhP15LyXn12IqIFBLgUqQGMRPe86k%3d>. It seems that using a parallel mono environment <http://www.mono-project.com/docs/compiling-mono/parallel-mono-environments/> 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 <https://github.com/mono/mono>.
Thanks for your help, Rick
_______________________________________________ Mono-devel-list mailing list [email protected] http://lists.dot.net/mailman/listinfo/mono-devel-list
