[Mono-devel-list] Splitting up Mono packages.

Andreas Nahr ClassDevelopment at A-SoftTech.com
Tue Mar 16 15:58:41 EST 2004


I',m usually not using Linux. However I think that you overlooked quite some
dependencies/ problems:

> mono-core:
> mono runtime, mcs.exe mscorlib.dll, System.dll, System.Xml.dll,
> Mono.Security.dll, I18n.
> deps: icu, libgc, glib.

Either move mcs.exe into its own package and have the chance that people
will get errors with this package (System.dll uses mcs.exe).
Or move mbas.exe (and probably Microsoft.VisualBasic.dll) into this package
because System.dll also uses mbas.exe.
mbas.exe also depends on Mono.GetOptions (which should probably be moved
into mbas.exe anyway as I'm not aware that this is used anywhere else)

> mono-remoting:
> System.Runtime.Remoting, System.Runtime.Remoting.Soap

The second assembly should should probably mean:
However these depend on System.Web.dll and System.Web.Services (and
obviously core) -  See System.Web

> mono-directory:
> Novell.LDAP, System.DirectoryServices

These could stay independent as they have no external dependencies (except -
of course - core)

> mono-asp-net:
> System.Web.dll, System.Web.Services.dll
> deps: mono-core

Dependencies are core, System.Drawing, System.Data,
System.EnterpriseServices (which adds: mono-directory, mono-remoting) - so
basically everything we have (except SWF)
So I would suggest to make:
System.Web.dll, System.Web.Services.dll, System.EnterpriseServices,
System.Runtime.Remoting, System.Runtime.Serialization.Formatters.Soap.dll
deps: core, mono-directory, mono-drawing, mono-data (see below)

Another idea would be to also put the core data assemblies in here (however
then mono-web would not make much sense)

> mono-windows-forms:
> System.Windows.Forms.dll
> Accessibility.dll
> Direct3D managed api.
> deps: mono-drawing, winelib, wine.

deps: mono-core
If we want to implement a D3D managed it should surely be moved into its own
package because it will probably add LOTs of additional dependencies
Also MS SWF has a dependency on
System.Runtime.Serialization.Formatters.Soap.dll. Mono does not have that
now. However if it is likely that we need that too (or want to add it for
compatibility reasons) we should probably put
System.Runtime.Serialization.Formatters.Soap.dll into its own package

> mono-db:
> All the database providers here

System.Data depends on System.EnterpriseServices which again depends on
Trying to separate anything really gets stupid at this point
We should have a mono-data that only contains anything neccesary for
and another:
for all other databaseproviders

> mono-jscript:
> Microsoft.JScript.dll
> jscript.exe


> mono-mbas:
> mbas.exe
> Microsoft.VisualBasic.dll

Should be moved into core (see above)

> mono-core-devel:
> monodis, ilasm, resgen, all the other small tools.
> deps: mono-core, pkg-config

Probably more dependencies (haven't checked)

> type-reflector:
> Only type-reflector
> deps; mono-core, gtk#


> mono-drawing:
> System.Drawing.dll
> Deps: cairo, libgdiplus, mono-core


> mono-other:
> Mono.*

Ok for the rest

We also should have:
System.Design.dll, System.Drawing.Design.dll
Deps: probably everything


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ximian.com/pipermail/mono-devel-list/attachments/20040316/ac4d9302/attachment.html 

More information about the Mono-devel-list mailing list