[Mono-devel-list] Splitting up Mono packages.
Miguel de Icaza
miguel at novell.com
Mon Mar 15 23:22:41 EST 2004
Hello,
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-core:
mono runtime, mcs.exe mscorlib.dll, System.dll, System.Xml.dll,
Mono.Security.dll, I18n.
deps: icu, libgc, glib.
mono-other:
Mono.*
mono-remoting:
System.Runtime.Remoting, System.Runtime.Remoting.Soap
mono-directory:
Novell.LDAP, System.DirectoryServices
mono-core-devel:
monodis, ilasm, resgen, all the other small tools.
deps: mono-core, pkg-config
type-reflector:
Only type-reflector
deps; mono-core, gtk#
mono-drawing:
System.Drawing.dll
Deps: cairo, libgdiplus, mono-core
mono-asp-net:
System.Web.dll, System.Web.Services.dll
deps: mono-core
mono-windows-forms:
System.Windows.Forms.dll
Accessibility.dll
Direct3D managed api.
deps: mono-drawing, winelib, wine.
mono-db:
All the database providers here
mono-jscript:
Microsoft.JScript.dll
jscript.exe
mono-mbas:
mbas.exe
Microsoft.VisualBasic.dll
Ideas?
Miguel.
More information about the Mono-devel-list
mailing list