We Ubuntu users are still very inconvenienced by that quick "we don't build" answer. Thanks for fixing the builder so that I can _try_ to home-build a .NET 2 version. After killing and reinstalling my Ubuntu system, I gave up trying to actually accomplish it. It requires installing a second version of Mono side-by-side with the supported version in order to do the build. But to do _that_ you have to home-build the newer version of Mono from source and ... [cough. sputter. Huh? ... Oh! ... Sorry! I'm back now...] I note that the IPy daily build script actually does build an appropriate version, but apparently the output gets thrown away. I would be very nice if it were put someplace where one could find it. Hopefully the next release of Ubuntu will have an upgraded .NET 4 compatible version of Mono, and this problem will go away. Until then, I still cannot use a current version of IronPython on my preferred workstation ... and therefore cannot do much IPy testing. (I only use Windows when I must, or when someone pays me to.) -- Vernon Cole (Typed on Ubuntu Linux 11.04)
On Mon, Jun 20, 2011 at 9:53 AM, Jeff Hardy <[email protected]> wrote: > On Sun, Jun 19, 2011 at 11:07 PM, Markus Schaber > <[email protected]> wrote: > > Are there no 3rd-party applications which embed and install IronPython > > with their own installer? > > > > Being afraid of such scenarios was the main reason why we build > > IronPython on our own (with changed assembly name and signing key) and > > install that customized version with our CoDeSys installer. > > Yes, but I think everyone chooses the same path you do > (rebuild/resign). At least, I'm pretty sure that's what Resolver One > does (I don't know of any other apps ... maybe we need a "Who's > Using?" page). > > The official installer is downgrade-proof, so other apps should just > be using that; if anyone else unconditionally puts the IronPython > files in the GAC, I'm not sure there's much we can do about it, sadly. > Polite requests and public shaming is about it. > > For embedding, I would recommend you continue what you're doing - it's > just just straight-up safer. It's a shame zipimport doesn't work; we > could cut the deployed size of the stdlib down significantly. > > > > > (The other reason was some suspected collision between the versions > > compiled for .NET 2.0 and 4.0. We wanted to avoid problems if users > > install their own IronPython versions. Nowadays, I'm convinced that this > > problem only arises if you compile an application for .net 4.x which > > references an IronPython dll compiled for .NET 2.x. > > Different signing keys for .NET 2 and .NET 4 would solve that. Since > we don't build for .NET 2 anymore it shouldn't be an issue, right? > > - Jeff > _______________________________________________ > Ironpython-users mailing list > [email protected] > http://mail.python.org/mailman/listinfo/ironpython-users >
_______________________________________________ Ironpython-users mailing list [email protected] http://mail.python.org/mailman/listinfo/ironpython-users
