[Mono-devel-list] Splitting up Mono packages.
A Rafael D Teixeira
rafaelteixeirabr at hotmail.com
Wed Mar 17 14:27:44 EST 2004
>From: "Andreas Nahr" <ClassDevelopment at A-SoftTech.com>
>I',m usually not using Linux. However I think that you overlooked quite
> > 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)
Well, FYI, some mono utilities also use Mono.GetOptions, like monocov. Also
people are using it in their projects outside mono, I know because I receive
emails asking for features, so it should continue to exist independently.
What I MAY do, JUST FOR mbas, is maybe compile the Mono.GetOptions sources
(except the one with the assembly-level attributes) inside mbas, but I
surely would prefer to have it in Mono.* as Miguel suggested, or if mbas is
moved to mono-core, that Mono.GetOptions moves there too.
General qustions to the list:
Are we talking about just executables/libraries, or this splitting is for
If the second would we still have an 'umbrella' Makefile equivalent to what
we currently have in /mcs? Maybe in the master package that brings up all
the others, as Miguel said?
Funny bits for all,
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