[Mono-devel-list] Splitting up Mono packages.
jaak at zd.com.pl
Tue Mar 16 05:29:58 EST 2004
What's wrong with Runtime vs SDK separation as it is done in .NET ?
Why do you want to isolate DirectoryServices, Drawing, ASP.NET, ADO.NET, SWF
Is this related to the patent issues ? Unless there are legal problems, I
wouldn't split mono at all.
The great thing about .NET is that you don't have to worry about
dependencies or system differences. You just assume that all the core stuff
needed to run your app is there ready to use.
----- Original Message -----
From: "Miguel de Icaza" <miguel at novell.com>
To: <mono-devel-list at ximian.com>
Sent: Tuesday, March 16, 2004 5:22 AM
Subject: [Mono-devel-list] Splitting up Mono packages.
> After the 0.31 release, we want to split up mono in various packages
> with dependencies, and we might find the help of the Debian people
> useful here, since they like to split things up.
> The basic is to have the Mono core separated from the higher level
> libraries which bring too many deps on us. This is an initial idea:
> mono runtime, mcs.exe mscorlib.dll, System.dll, System.Xml.dll,
> Mono.Security.dll, I18n.
> deps: icu, libgc, glib.
> System.Runtime.Remoting, System.Runtime.Remoting.Soap
> Novell.LDAP, System.DirectoryServices
> monodis, ilasm, resgen, all the other small tools.
> deps: mono-core, pkg-config
> Only type-reflector
> deps; mono-core, gtk#
> Deps: cairo, libgdiplus, mono-core
> System.Web.dll, System.Web.Services.dll
> deps: mono-core
> Direct3D managed api.
> deps: mono-drawing, winelib, wine.
> All the database providers here
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
More information about the Mono-devel-list