There is now a tarball available for MonoDevelop 6.0.
This bug should contain the issues that still need to be worked out to package MonoDevelop 6 for Fedora Rawhide.
The source of the spec file and the patches is currently maintained at https://github.com/tpokorra/lbs-mono-fedora/tree/ALPHA/monodevelop
MonoDevelop has an addin for NUnit2 and NUnit3 runners.
We need to decide if we upgrade the nunit package in Fedora from NUnit2 to NUnit3, or if we add a new package nunit3.
For the moment, I have disabled nunit3 in my working copy of the MonoDevelop6 spec file.
There is an adding RefactoringEssentials which requires the PCL reference assemblies (see also http://stackoverflow.com/questions/35245840/build-monodevelop-on-debian-jessie-using-mono-4-3-3).
We cannot use reference assemblies in Fedora, so I suggest we drop that addin, as I have done in my working copy of the MonoDevelop spec file.
Another missing assemblies is System.Collections.Immutable
It is used by src/core/MonoDevelop.Core/MonoDevelop.Core.csproj
It comes with the tarball, but we drop precompiled assemblies for Fedora.
So we probably need to create a new package for System.Collections.Immutable.
(In reply to Timotheus Pokorra from comment #1)
> MonoDevelop has an addin for NUnit2 and NUnit3 runners.
> We need to decide if we upgrade the nunit package in Fedora from NUnit2 to
> NUnit3, or if we add a new package nunit3.
> For the moment, I have disabled nunit3 in my working copy of the
> MonoDevelop6 spec file.
In my opinion the best is update nunit to v3 and if necessary add a new package nunit2 for compatibility
another added dependancy is fsharp. but perhaps we can patch that out.
This bug appears to have been reported against 'rawhide' during the Fedora 25 development cycle.
Changing version to '25'.
Another issue is the assembly external\roslyn\Binaries\Release\Microsoft.CodeAnalysis.dll used in src/core/MonoDevelop.Core/MonoDevelop.Core.csproj
we need to compile that from source somehow.
Licensed under the Apache License, Version 2.0.
initial work for package mono-immutablecollections which packages System.Collections.Immutable from https://github.com/mono/ImmutableCollections:
removed references to FSharp and RefactoringEssentials:
I have upgraded NUnit to version 3 in Rawhide.
curious question: why are you packaging ImmutableCollections from mono:
and not the one from .NET:
@Ondra: it is a good question. I am not sure yet. I actually don't know if there are technical limitations of packages targetted for .NET core, if they can be used with Mono?
let's ask Monodevelop developers: https://bugzilla.xamarin.com/show_bug.cgi?id=43322
hi, there is news about the release?
I have done some work on this in September 2016, but not since then.
so the current status is as described on my blog:
* I am building my own tarball at https://lbs.solidcharity.com/package/tpokorra/mono/monodevelop-tarball. It is currently probably too big, but I download all referenced packages from nuget and include them in the tarball.
* I have made some progress building MonoDevelop 6 for Fedora. At the moment, I have disabled FSharp (cannot build it with xbuild IIRC), and code analysis as well, due to missing .NET portable reference assemblies (they are trying to open source them: http://lists.dot.net/pipermail/monodevelop-list/2016-November/016519.html).
this is my current copr for MonoDevelop 6:
If you have a chance to test it, please let me know if that would work for you.
Still it would be a lot of work to get this into Fedora properly, because we cannot just use packages from nuget.
This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle.
Changing version to '26'.
"Support for C/C++ was removed in MonoDevelop 6.0 since it did not work."
And the latest stable version of MonoDevelop is 126.96.36.199.
But the latest stable version that supports C/C++ is 188.8.131.52.
I think Fedora should upgrade MonoDevelop to 184.108.40.206, and add 220.127.116.11
(keep two versions, monodevelop5 and monodevelop7).
Unfortunately, there is no tarball available for MonoDevelop 18.104.22.168.
I have now asked upstream.
Regarding C/C++ development with MonoDevelop: are you actually using that? does it work?
MonoDevelop download page archived on 2016.01.28 shows 22.214.171.124.
Can you find it in http://download.mono-project.com/sources/monodevelop/?
Why the tarballs must in http://download.mono-project.com/sources/monodevelop/?
Who tell you?
I can not understand your strange logic.
MonoDevelop 5 supports C/C++.
But MonoDevelop 6 and MonoDevelop 7 are not.
It seems that I talked about an old story.
Okay, just talk about current.
Current MonoDevelop download page shows 126.96.36.199.
Can you find it in http://download.mono-project.com/sources/monodevelop/?
But I can find it in GitHub:
The issue is that the tarball on Github is just a snapshot of the source code at that point in time.
It does not include submodules referenced through git etc.
So the tarball from Github would not be sufficient for packaging MonoDevelop.
The other issue is, starting with MonoDevelop 6, Xamarin has given up building RPM packages, and are now only delivering MonoDevelop as a Flatpak.
The additional challenge for Fedora is, that we don't just want to include binaries from upstream or Nuget, but build everything from source.
This makes it very difficult to build MonoDevelop 6 or 7, as you can see from the comments above in this bug report.
I am sort of waiting for things to move forward on the dotnet core front in Fedora, and to have msbuild available on Fedora. Then it might be possible, but still a lot of work, to build the nuget packages in Fedora.
A first step was to build MonoDevelop 6 in a copr. I did that in February 2017, but I did not get any feedback. Do you think I should build MonoDevelop 7 in that copr? Would you help with testing?
It is still a huge task. I don't have the time right now. Any volunteers?
Here is what I currently got.
I chose monodevelop 188.8.131.521 because the flatpak on http://www.monodevelop.com/download/ has that version.
dnf install which git autoconf automake mono-devel mono-winfx
# for nuget, downloading packages
# looking at https://git.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=packages/fsharp
git clone https://github.com/fsharp/fsharp
git checkout tags/4.1.18 -b fsharp-4.1.18
# make DESTDIR="$pkgdir" install
# looking at https://git.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=packages/monodevelop
dnf install intltool gnome-sharp-devel monodoc-devel cmake libssh2-devel
# flatpak hat Version: https://github.com/mono/monodevelop/releases/tag/monodevelop-184.108.40.2061
git clone https://github.com/mono/monodevelop.git monodevelop
git checkout tags/monodevelop-220.127.116.111 -b monodevelop-18.104.22.1681
git submodule update --init --recursive
./configure --prefix=/usr --profile=stable
XDG_CONFIG_HOME="`pwd`"/config LD_PRELOAD="" make
It fails with:
make: msbuild: Command not found
I did try to build msbuild some time ago but did not succeed: https://github.com/tpokorra/lbs-mono-fedora/issues/22
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora 'version'
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 26 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
This bug appears to have been reported against 'rawhide' during the Fedora 29 development cycle.
Changing version to '29'.
I guess after we have Mono 5 in Fedora again, we should consider if it is possible to build a recent version of MonoDevelop for Fedora again, or if we should give up and let people use the flatpak provided by Xamarin/Microsoft?
It seems Debian will not have Monodevelop in the upcoming 10th release aka Buster anymore (https://packages.debian.org/de/stretch/monodevelop).