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

[Lluis Sanchez]

On dt, 2004-03-16 at 21:58, Andreas Nahr wrote:
> 
> 
> > mono-remoting:
> > System.Runtime.Remoting, System.Runtime.Remoting.Soap
> 
> The second assembly should should probably mean:
> System.Runtime.Serialization.Formatters.Soap.dll
> However these depend on System.Web.dll and System.Web.Services (and
> obviously core) -  See System.Web

System.Web.Services is not needed. System.Web is needed because remote
objects can be hosted in XSP.

Lluis.

> 
> 
> >
> > 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:
> mono-web:
> 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
> System.Web....
> Trying to separate anything really gets stupid at this point
> We should have a mono-data that only contains anything neccesary for
> System.Web
> and another:
> mono-data-providers
> for all other databaseproviders
> 
> 
> > mono-jscript:
> > Microsoft.JScript.dll
> > jscript.exe
> 
> Ok
> 
> 
> > 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#
> 
> Ok
> 
> 
> >
> > mono-drawing:
> > System.Drawing.dll
> > Deps: cairo, libgdiplus, mono-core
> 
> Ok
> 
> 
> > mono-other:
> > Mono.*
> 
> Ok for the rest
> 
> 
> We also should have:
> mono-design:
> System.Design.dll, System.Drawing.Design.dll
> Deps: probably everything
> 
> 
> Andreas
>