[Pkg-mono-devel] Re: Mono Debian Packaging

[Paolo Molaro]

On 01/20/04 Eduard Bloch wrote:
> > > *) later, I'd like for debian to have a package with just the base
> > > assemblies (mscorlib, System, System.Xml) and one (or more) separate
> > > packages for the rest of the assemblies.
> > at the moment the mono-assemblies-base has all arch independent
> > assemblies, and mono-assemblies-arch for the other, mono-assemblies-* is
> > still open for others things.. not sure yet how we do this.
> 
> Yeah. Remember, we considered creating mono-assemblies-core and
> mono-assemblies-$component but it was not clear how to separate them
> perfectly.

The bare minimal is mscorlib alone. The next step would be System.dll +
System.Xml.dll (maybe with System.Drawing). After that things become more 
complicated, but, for example, the database-related assemblies could be 
their own package.

> It was introduced by Alp or ElectricElf... the idea was probabaly to
> provide a way to install alternative classes packages, eg. from the
> DotGNU project.

Yes, but as it is used currently it can't be used that way anyway.
Remember that mscorlib.dll and System.dll are tightly coupled with the
runtime: they won't work with other runtimes (they may well not work
with different versions of mono).
The high-level stuff is different, but it depends on a per-assembly
basis and can't be easily managed with packages (maybe using
alternatives, but at this point in time it would result in a mess).

lupus

-- 
-----------------------------------------------------------------
lupus@debian.org                                     debian/rules
lupus@ximian.com                             Monkeys do it better