[Mono-devel-list] Splitting up Mono packages.
A Rafael D Teixeira
rafaelteixeirabr at hotmail.com
Tue Mar 16 13:24:11 EST 2004
>From: Dan Winship <danw at ximian.com>
> > mono-core:
> > mono runtime, mcs.exe mscorlib.dll, System.dll, System.Xml.dll,
> > Mono.Security.dll, I18n.
> > deps: icu, libgc, glib.
>mcs.exe doesn't really belong with the other things there... you can run
>mono apps fine without having a compiler. Seems like it would make sense
>to put that in mono-core-devel.
Most people forget that any managed code can invoke the compilers
(mcs/mbas/jscript) at any time (the wrapping classes live in System.dll, or
More specifically any ASP.NET applications inherently call the compilers AT
RUNTIME as pages get updated, or simply are executed for the first time.
That's why mcs is in mono-core. If not we would need an special
mono-compilers package, that would be a dependency for both ASP.NET and
mono-core-devel packages. I prefer to keep it in mono-core.
BTW: mbas isn't there because it isn't mature enough (my fault), but be
sure, many developers coming from the windows world keep asking for it,
especially for ASP.NET development with Mono, so for Mono 1.2 I'm quite sure
it will be there in mono-core, also.
Rafael "Monoman" Teixeira
Mono Hacker since 16 Jul 2001 - http://www.go-mono.org/
MonoBrasil Founding Member - Membro Fundador do MonoBrasil
English Blog: http://monoblog.blogspot.com/
Brazilian Portuguese Blog: http://monoblog.weblogger.terra.com.br/
MSN Messenger: instale grátis e converse com seus amigos.
More information about the Mono-devel-list