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 <http://lists.ximian.com/pipermail/mono-list/2016-August/052160.html>. I assume this was related to the removal of the static libmono from some packages <http://lists.ximian.com/pipermail/mono-packagers-list/2016-February/000223.html> .
Rick On Tue, Aug 23, 2016 at 3:13 PM, Greg Young <[email protected]> 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 <[email protected]> > 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 > > [email protected] > > http://lists.dot.net/mailman/listinfo/mono-devel-list > > > > > > -- > Studying for the Turing test >
_______________________________________________ Mono-devel-list mailing list [email protected] http://lists.dot.net/mailman/listinfo/mono-devel-list
