Package: libfsharp-core4.3-cil
Version: 3.1.1.26+dfsg2-1
Severity: important

Dear Maintainer,

Upstream F# installs the following FSharp.Core assemblies:

2.3.0.0 in /usr/lib/mono/2.0/
4.3.0.0 in /usr/lib/mono/4.0/
4.3.1.0 in /usr/lib/mono/4.5/

In Debian, we install to the policy folder /usr/lib/cli/FSharp.Core-4.3/ then
add the following symlinks:

/usr/lib/mono/4.0/FSharp.Core.dll ->
/usr/lib/cli/FSharp.Core-4.3/FSharp.Core.dll (4.3.1.0)
/usr/lib/mono/4.5/FSharp.Core.dll ->
/usr/lib/cli/FSharp.Core-4.3/FSharp.Core.dll (4.3.1.0)

In this day & age, missing out on the 2.3.0.0 assembly isn't a big deal, but
the missing 4.3.0.0 assembly is problematic for building any projects which
support older F# revisions, as they tend to use a versioned dependency on
4.3.0.0 for compilation (then execute fine on 4.3.1.0, via the GAC policy)

Since F# is a framework rather than a bog-standard library, I feel it would be best to follow the upstream path behaviour rather than using the more general
GAC policy path



-- System Information:
Debian Release: jessie/sid
  APT prefers trusty-updates
APT policy: (500, 'trusty-updates'), (500, 'trusty-security'), (500, 'trusty'), (100, 'trusty-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.13.0-37-generic (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libfsharp-core4.3-cil depends on:
ii  cli-common                      0.9
ii  libmono-corlib4.5-cil           3.10.0-0xamarin1
ii  libmono-system-core4.0-cil      3.10.0-0xamarin1
ii  libmono-system-numerics4.0-cil  3.10.0-0xamarin1
ii  libmono-system4.0-cil           3.10.0-0xamarin1
ii  mono-runtime                    3.10.0-0xamarin1
ii  mono-runtime-common             3.10.0-0xamarin1

libfsharp-core4.3-cil recommends no packages.

libfsharp-core4.3-cil suggests no packages.

-- no debconf information


--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to