- 1 Mono 4
- 1.1 Summary
- 1.2 Owner
- 1.3 Current status
- 1.4 Detailed Description
- 1.5 Benefit to Fedora
- 1.6 Scope
- 1.7 Upgrade/compatibility impact
- 1.8 How To Test
- 1.9 User Experience
- 1.10 Dependencies
- 1.11 New packages for mono stack
- 1.12 Contingency Plan
- 1.13 Documentation
- 1.14 Release Notes
Update the Mono stack in Fedora from 2.10 to 4.*
- Name: Claudio Rodrigo Pereyra Diaz
- Email: <email@example.com>
- Release notes owner:
Support for Mono versions 3.0 and 2.10 has been discontinued. No further development of bug fixing is planned for those branches. Mono 4 is the active branch and has many improvements. See upstream notes http://www.mono-project.com/docs/about-mono/releases/4.0.0/
Mono requires itself to build. The Mono version 2.10.8 currently included in Fedora is too old to build version 4 that requires at least version 3.4. At the moment on copr we use monolite, a little version of mono compiler shipped in the tarball for first build time.
We have two options to upgrade:
- Upgrade mono to version 3.4, then to version 3.12 and then to version 4.0.1 on rawhide (3.4 now builds on rawhide: https://copr.fedoraproject.org/coprs/tpokorra/mono-3.4/monitor/)
- Make a one time exception of the rule for build mono 4.0.1-1 using monolite, later make mono depend again on it self and rebuild mono 4.0.1-2 using mono-4.0.1-1
- this is the favoured option, because there are new architectures anyway: armv7hl, aarch64, ppc64, ppc64l
- it would be best to bootstrap Mono 4 for all of the primary and secondary architectures at the same time (https://fedoraproject.org/wiki/Architectures#Structure)
- there is now an FPC ticket for this: https://fedorahosted.org/fpc/ticket/528
Steps for Bootstrapping
- The Monolite binaries are included in the Mono tarball which is provided by upstream. see also http://www.mono-project.com/docs/advanced/monolite/
- Monolite is a minimal binary distribution of mcs. This is the compiler that is able to build the rest of Mono.
- In the spec file, we usually delete all dlls and executables before the build section.
- For the bootstrap, we would once keep the monolite binaries.
- After Mono has been built for all primary and secondary architectures, and for Epel, we enable the deletion of the monolite binaries again in the spec file.
Benefit to Fedora
Fedora aims to showcase the latest in free and open source software - we should have the most recent release of Mono 4.0.1
It will have the ability to run cross-platform applications that require compatibility with Microsoft. Net Framework 4.5
- Proposal owners:
Update mono spec and build in copr and/or koji until is ready.
- Other developers:
See Upgrade/compatibility impact and Dependencies section
- Release engineering: None
- Policies and guidelines: None
Mono 4 includes most of the features of Mono 2.10 and Mono 3 branch.
The profiles 2.0, 3.5 and 4.0 will not be build any more in favor of profile 4.5
Many packages may need to be revised, updated or rebuilt because Mono 4 require that all application use target 4.5. In general is a simple task to sed .sln, .cproj, configure, configure.in, configure.am, Makefile, Makefile.in, Makefile.am for use mcs instead gmcs and change profile < 4.5 to 4.5. The files to sed change depending in what form is distributed the sources. In most off the cases only configure files need sed. A few package work without changes like gnome-subtitle or pinta
How To Test
Interested testers do not need special hardware. Take a given Mono application and test it against the Mono at this copr repo and verify it works:
User should note speedy improvement running Mono applications.
Some applications will have features only supported if used Mono 4
New packages for mono stack
|Package||In Copr||Status||In Rawhide||Notes|
|gtk-sharp3||Yes||Done||2.99.3-11.fc23||Build in koji http://koji.fedoraproject.org/koji/buildinfo?buildID=637565|
- Contingency mechanism: Still in Mono 2.10
- Contingency deadline: Beta freeze
- Blocks release? No
- Blocks product? Monodevelop >= 5