[Mono-dev] One Version of Mono.Cairo

[Miguel de Icaza]

Hello,

> Currently we ship 2 versions of Mono.Cairo.dll in Mono, a 1.0 and a 2.0 
> version.  However, there is no difference in these versions.  This can 
> cause issues if different assemblies reference different versions and 
> the runtime tries to load them both.
> 
> I think we need to:
> - Not ship a 2.0 version.
> - Ship a policy file that maps both versions to the 1.0 version.

For now, this makes sense.   Can we ask Hari to look into this?

On the long term though, we have to consider whether it would be useful
for us to only provide certain functionality on the 2.0 profile that
might depend on new classes from 2.0 or generics.

> Some other assemblies that we appear to ship 1.0 and 2.0 versions of 
> without any differences between them (looking at the 1.9.1 Win/Mono Gac):
> - CustomMarshallers.dll
> - Mono.Data.dll
> - Mono.Data.SybaseClient.dll
> - Mono.Data.TdsClient.dll
> - Mono.Http.dll
> - Mono.Posix.dll
> - Mono.Security.Win32.dll
> - Novell.Directory.Ldap.dll
> - Npgsql.dll
> - OpenSystem.C.dll

Agreed, we should also make these changes;   There is no reason to ship
both for now.