Date: Fri, 25 Aug 2017 20:50:18 +0100 From: Alexander Regueiro <alexreg@gmail.com> To: David Naylor <naylor.b.david@gmail.com> Cc: freebsd-mono@freebsd.org, =?utf-8?Q?Romain_Tarti=C3=A8re?= <romain@freebsd.org> Subject: Re: Update on porting mono 5 Message-ID: <DE259F69-EC05-4EB0-A52A-9D9CCD904E65@gmail.com> In-Reply-To: <3186981.TyGdqNibkJ@dragon.local> References: <17078253.u2dgjZK1Z6@dragon.local> <20170815102120.GA29251@blogreen.org> <3186981.TyGdqNibkJ@dragon.local>
next in thread | previous in thread | raw e-mail | index | archive | help
What about getting mono to actually build first? Sent from my iPhone > On 25 Aug 2017, at 20:41, David Naylor <naylor.b.david@gmail.com> wrote: >=20 >> On Tuesday, 15 August 2017 12:21:20 Romain Tarti=C3=A8re wrote: >> Hi David, >>=20 >>> On Tue, Aug 15, 2017 at 09:11:57AM +0200, David Naylor wrote: >>> Here is an update on porting mono 5: >>> - mono: 5.1.0.1 (needs to be updated to 5.2, tests run) >>> - msbuild: 15.3 (needs tests ported and run, upstream bugs filed) >>> - fsharp: 4.1.25 (WIP) >>> - monodevelop: 7.0.1.24 (WIP) >>> - gtksharp20: 2.12.45 (WIP) >>> - avahi-sharp: 0.7 (not started) >>> - bumping all dependent ports (not started) >>> - exp-run (not started) >>>=20 >>> Would anyone be interested in doing a (Phabricator) review? >>=20 >> I don't actively use mono nowadays but sure, I can check if my old code >> tests suites still pass with the update. I have just registered to >> Phabricator and have no previous experience with this tool, so get ready >> to teach me stuff ;-) >=20 > Great, thanks. =20 >=20 > Here is a status update (with patch [1][3]). Things aren't ready yet, but= as=20 > it=20 > stands: > - lang/mono: 5.2.0.215 (tests failing in mcs/class/corlib [run-test-local]= ) > - devel/msbuild: 15.3 (tests failing [with SIGABRT]) > - lang/sharp: 4.1.25 (tests failing in math/measures/test.fsx [Invalid IL=20= > code]) > - x11-toolkits/gtk-sharp20: 2.12.45 > - x11-toolkits/gnome-sharp20: 2.24.4 > WIP: > - devel/monodevelop: 7.1.0.1297 (full nuget package restore required [extr= a=20 > nuget support required]) > - devel/mono-addins: depreciate [2] (broken with mono5), fix dependencies > TODO: > - mono: test self hosting > - update mono-lite version > - avahi-sharp: 0.7 > - bump all dependent ports > - exp-run > - commit to ports > - upstream patches > - fix tests >=20 > Note that the failing tests don't worry me too much. Most of them are edg= e=20 > cases that won't affect the average user (i.e. not a blocker to commit to=20= > ports) - also I don't know how many tests are failing on other platforms (= if=20 > any). =20 >=20 > [1] git clone https://github.com/DragonSA/ports; cd ports; git diff=20 > master..origin/mono5.2.0.215 > [2] A general discussion needs to be had around nuget packages. How do we= =20 > consume them? > i) as downloads with each port containing a copy > ii) local ports with consistency across the Ports Collections > iii) A mixture of the above (i.e. (ii) is there is a native component,=20 > otherwise (i)) > I prefer (ii) as I think it gives the end user the best leverage to patch=20= > issues with nuget packages locally (and to get updates without waiting on a= )=20 > upstream, and b) us/ports maintainer). However, at this point that option= is=20 > at 0% progress. =20 > [3] https://people.freebsd.org/~dbn/mono-20170825.diff.xz
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?DE259F69-EC05-4EB0-A52A-9D9CCD904E65>