[Mono-dev] Distribute Parallel Mono Environment?
rtillerywork at gmail.com
Tue Aug 23 20:54:05 UTC 2016
Sorry, I didn't mean to imply mkbundle was deprecated. I was told that the
--static argument was deprecated by someone at Xamarin/Microsoft, and
linked to the newer mkbundle
assume this was related to the removal of the static libmono from some
On Tue, Aug 23, 2016 at 3:13 PM, Greg Young <gregoryyoung1 at gmail.com> wrote:
> Where did you see mkbundle being depreceated (I ask as we use this).
> On Tue, Aug 23, 2016 at 9:10 PM, Rick Tillery <rtillerywork at gmail.com>
> > 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
> > been deprecated.) So, what is the recommended way to distribute a
> > 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
> > 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
> Studying for the Turing test
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Mono-devel-list