Hi, guys!
Sorry for late response.
I agree to remove Npgsql from mono and use the nuget packages. This
approach is more streamlined with the idea of modularity of the packages.
The user should only have Npgsql.dll in her system if she really is going
to use it.
P.S.: I'd like to use this
Hello,
On 2014年11月28日 02:19, Alexander Köplinger wrote:
Hey,
* gmcs/dmcs - they just redirect to mcs now and without the
2.0 etc profiles it doesn't make sense to still have them
I like to keep them, to avoid breaking third party build scripts.
Good point, however
Let's remove my Commons.Xml.Relaxng. It is really isolated work.
Atsushi Eno
On 2014年11月28日 00:01, Alexander Köplinger wrote:
Judging from the recent version bump in git to 3.99 it looks like the
next release after 3.12 will be Mono 4.0.
As this is a major release it'll allow us to remove
Before we go down this path.
Mono 4.0 is not about a general call to clean things up. We are only
cleaning up removing the must-haves.
Please do not turn this into a threat to clean this up. That can be done
independently and on its own schedule.
Atsushi, I'll follow up later today on
I agree with removing Npgsql from Mono. Or either convince someone to commit
the latest version of Npgsql to mono. It would have to build with mono's build
system though. Francisco?
The main reason it was included in mono was so you could have an out-of-the-box
experience with mono
@lists.ximian.com
Subject: Re: [Mono-dev] List of cleanup candidates for Mono 4.0
I agree with removing Npgsql from Mono. Or either convince someone to commit
the latest version of Npgsql to mono. It would have to build with mono's build
system though. Francisco?
The main reason it was included
...@my2cents.co.uk; alex.koeplin...@outlook.com
CC: mono-devel-list@lists.ximian.com
Subject: Re: [Mono-dev] List of cleanup candidates for Mono 4.0
I agree with removing Npgsql from Mono. Or either convince someone to
commit the latest version of Npgsql to mono. It would have to build with
mono's
: mig...@xamarin.com
Date: Sat, 29 Nov 2014 12:04:12 -0500
Subject: Re: [Mono-dev] List of cleanup candidates for Mono 4.0
To: alex.koeplin...@outlook.com
CC: monodanm...@yahoo.com; mono-devel-list@lists.ximian.com
Hey,
We want to implement the same .NET Core interface when it becomes available
. a core contributor asking us to remove it from Mono:
https://bugzilla.xamarin.com/show_bug.cgi?id=23119
-- Alex
--
From: mig...@xamarin.com
Date: Sat, 29 Nov 2014 12:04:12 -0500
Subject: Re: [Mono-dev] List of cleanup candidates for Mono 4.0
To: alex.koeplin
Judging from the recent version bump in git to 3.99 it looks like the next
release after 3.12 will be Mono 4.0.
As this is a major release it'll allow us to remove some cruft that is no
longer needed, so I thought I'd start a list of things I'd like to see removed:
* net2.0/4.0 profiles -
Hey Alex,
* gmcs/dmcs - they just redirect to mcs now and without the 2.0
etc profiles it doesn't make sense to still have them
I like to keep them, to avoid breaking third party build scripts.
The removal of frameworks requires that the upstream packages actually work
on Mono, and I do not
Hey,
* gmcs/dmcs - they just redirect to mcs now and without the 2.0 etc profiles
it doesn't make sense to still have them
I like to keep them, to avoid breaking third party build scripts. Good point,
however aren't they gonna break anyway when they rely on 2.0 SDK which is no
longer there
On 27.11.2014 19:19, Alexander Köplinger wrote:
Hey,
* gmcs/dmcs - they just redirect to mcs now and without the 2.0 etc profiles
it doesn't make sense to still have them
It doesn't make sense to us, but removing them would just break
thinks downstream.
It's really annoying when such changes
On 27 November 2014 at 18:19, Alexander Köplinger
alex.koeplin...@outlook.com wrote:
* aspnetwebstack (i.e. MVC+WebApi) - same reasons as for EF, open-source
and on NuGet, should be used from there
I am actually not sure about this one, is that really the case?
The latest
14 matches
Mail list logo
