Moving this conversation back to the Fedora mono list...
On 13 April 2015 at 13:29, Claudio Rodrigo elsupergomez@gmail.com wrote:
I think, Mono 3 and 4 must coexist like python 2 and python 3. Unless all software dependent on profiles 2, 3.5 and 4 migrate to profile 4.5. This is a huge task like I see, because many package depend on this profiles. What do you think?
I think the difference between Python2 and Python3 is much bigger, because the API has changed. You need to completely rewrite software from 2 to 3.
For profiles < 4.5, there are only minor issues I suspect. Can we hold the package maintainers of the other packages responsible for patching and fixing their packages for Mono 4?
I don't think we should maintain two different versions of Mono, if we have trouble maintaining just one...
Alternatively, we could first focus on getting Mono 3.12.1 into Fedora, before we start working on Mono 4 at all.
On Mon, 2015-04-13 at 14:17 +0200, Timotheus Pokorra wrote:
Moving this conversation back to the Fedora mono list... Alternatively, we could first focus on getting Mono 3.12.1 into Fedora, before we start working on Mono 4 at all.
Also, the Mono Project itself has opened their own repository for CentOS packages which have been working well on Fedora 21.
I've been using the 3.12.1 from there for the past couple of months for my OpenSimulator server and their build works without issue for me.
Perhaps that repo can be rolled into the mix and the effort here merged with the effort there for RPMs, and reporting bugs upstream?
Or at least the group here work with the people building and pushing those packages there?
http://www.mono-project.com/download/#download-lin
Perhaps that repo can be rolled into the mix and the effort here merged with the effort there for RPMs, and reporting bugs upstream?
Or at least the group here work with the people building and pushing those packages there?
You are completely right!
I got already some very good replies from Jo Shields, who nowadays works for Xamarin, and is also the Debian packager of Mono: http://lists.ximian.com/pipermail/mono-packagers-list/2015-April/000219.html
The issues are a little bit more complicated, to get Mono integrated into Fedora as a distribution, because a number of packages depend on it, and the rules for the packages are more stricter.
On 13 April 2015 at 13:29, Claudio Rodrigo elsupergomez@gmail.com wrote:
I think, Mono 3 and 4 must coexist like python 2 and python 3. Unless all software dependent on profiles 2, 3.5 and 4 migrate to profile 4.5. This is a huge task like I see, because many package depend on this profiles. What do you think?
I think the difference between Python2 and Python3 is much bigger, because the API has changed. You need to completely rewrite software from 2 to 3.
For profiles < 4.5, there are only minor issues I suspect. Can we hold the package maintainers of the other packages responsible for patching and fixing their packages for Mono 4?
I have now tried to use Keepass as an example of a package that targets an older Framework. I have added a couple of lines to fix the sln and csproj files. This will make sure it compiles even if only .Net Framework 4.5 is available, with Mono 4.5.
find . -name "*.sln" -print -exec sed -i 's/Format Version 10.00/Format Version 11.00/g' {} ; find . -name "*.csproj" -print -exec sed -i 's#ToolsVersion="3.5"#ToolsVersion="4.0"#g; s#<TargetFrameworkVersion>.*</TargetFrameworkVersion>##g; s#<PropertyGroup>#<PropertyGroup><TargetFrameworkVersion>v4.5</TargetFrameworkVersion>#g' {} ;
see context: https://github.com/tpokorra/lbs-mono-fedora/blob/master/keepass/keepass.spec...
I was not able to install the resulting rpm yet, due to other issues with the Mono4 alpha rpm (provides is still wrong)...
@Claudio: Thanks for the pull request on Github!
Somehow copr currently has a long queue. I will build on my own LightBuildServer for now: https://lbs.solidcharity.com/project/tpokorra/mono-fedora
When I am happy with the result, I will upload to copr again.
If you want an account on my LightBuildServer for your Mono packages as well, let me know!
When I am happy with the result, I will upload to copr again.
I have now uploaded Mono 4 alpha1, and also KeePass and MonoDevelop 5.7 to my copr account: https://copr.fedoraproject.org/coprs/tpokorra/mono/
Mono4 now even builds for Epel6 and Epel7, by disabling the debug package.
I also had to build new packages nunit and nuget, which are based off the Xamarin packages. Those spec files need to be cleaned up for Fedora standards, and probably the tarballs validated as well.
I was able to recompile gtk-sharp2, gnome-sharp, gnome-desktop-sharp and mono-addins against Mono4, with some sed replacements in the csproj files, as described in my previous email. The sources of all these packages are available here: https://github.com/tpokorra/lbs-mono-fedora
I am open for suggestions and improvements, and happy to merge pull requests.
Next steps: So should I go through the list of packages that depend on mono-core in Fedora 22, and rebuild them for Mono4, and people can test them from my copr repo?
This is how I get all packages that somehow depend on Mono: repoquery --whatrequires --recursive mono-core
Hi Timotheus,
On Thu, Apr 16, 2015 at 01:11:50PM +0200, Timotheus Pokorra wrote:
I have now uploaded Mono 4 alpha1, and also KeePass and MonoDevelop 5.7 to my copr account: https://copr.fedoraproject.org/coprs/tpokorra/mono/
Mono4 now even builds for Epel6 and Epel7, by disabling the debug package.
I am open for suggestions and improvements, and happy to merge pull requests.
Next steps: So should I go through the list of packages that depend on mono-core in Fedora 22, and rebuild them for Mono4, and people can test them from my copr repo?
This is how I get all packages that somehow depend on Mono: repoquery --whatrequires --recursive mono-core
First off, thank you for doing this work!
I'm completely new to the .Net/C# and Mono universe, but I've been using Fedora (and Redhat before that) for a very long time.
I have recently been assigned the task of migrating a .Net/C# application to Linux, and as such I'm currently using your packages to go through a few of the online C# tutorials :)
I'm *very* interested in seeing a recent (4.0+) version of Mono officially supported in Fedora, as that will have a much better chance of smoothing the migration of applications originally developed on Windows.
I do have some moderate packaging experience (I'm down to three Fedora packages, having orphaned a bunch of stuff I was no longer using professionally).
If I can be of any help (if nothing else, I plan to use your latest packages to learn c#, and generally serve as guinea pig), please let me know.
I wanted to at least start by add a "+1" to the effort of upgrading Fedora's official Mono package set to 4.0.X.
Thanks again, --Gabriel
Hello.
I fix more and more package to build with mono 4. I will update Change mono 3 proposal for F22 to mono 4 for F23 but I need sponsor for my package https://bugzilla.redhat.com/show_bug.cgi?id=1192059 to became packager and next co maintainer of mono. Some of you can do a formal review of gtk-sharp3 package and sponsor me?
Thanks.
2015-04-29 10:26 GMT-03:00 Gabriel L. Somlo gsomlo@gmail.com:
Hi Timotheus,
On Thu, Apr 16, 2015 at 01:11:50PM +0200, Timotheus Pokorra wrote:
I have now uploaded Mono 4 alpha1, and also KeePass and MonoDevelop 5.7 to my copr account: https://copr.fedoraproject.org/coprs/tpokorra/mono/
Mono4 now even builds for Epel6 and Epel7, by disabling the debug
package.
I am open for suggestions and improvements, and happy to merge pull
requests.
Next steps: So should I go through the list of packages that depend on mono-core in Fedora 22, and rebuild them for Mono4, and people can test them from my copr repo?
This is how I get all packages that somehow depend on Mono: repoquery --whatrequires --recursive mono-core
First off, thank you for doing this work!
I'm completely new to the .Net/C# and Mono universe, but I've been using Fedora (and Redhat before that) for a very long time.
I have recently been assigned the task of migrating a .Net/C# application to Linux, and as such I'm currently using your packages to go through a few of the online C# tutorials :)
I'm *very* interested in seeing a recent (4.0+) version of Mono officially supported in Fedora, as that will have a much better chance of smoothing the migration of applications originally developed on Windows.
I do have some moderate packaging experience (I'm down to three Fedora packages, having orphaned a bunch of stuff I was no longer using professionally).
If I can be of any help (if nothing else, I plan to use your latest packages to learn c#, and generally serve as guinea pig), please let me know.
I wanted to at least start by add a "+1" to the effort of upgrading Fedora's official Mono package set to 4.0.X.
Thanks again, --Gabriel _______________________________________________ mono mailing list mono@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/mono
I just move Change proposal from mono 3 to mono 4.
See https://fedoraproject.org/wiki/Changes/Mono_4
2015-04-29 14:28 GMT-03:00 Claudio Rodrigo elsupergomez@gmail.com:
Hello.
I fix more and more package to build with mono 4. I will update Change mono 3 proposal for F22 to mono 4 for F23 but I need sponsor for my package https://bugzilla.redhat.com/show_bug.cgi?id=1192059 to became packager and next co maintainer of mono. Some of you can do a formal review of gtk-sharp3 package and sponsor me?
Thanks.
2015-04-29 10:26 GMT-03:00 Gabriel L. Somlo gsomlo@gmail.com:
Hi Timotheus,
On Thu, Apr 16, 2015 at 01:11:50PM +0200, Timotheus Pokorra wrote:
I have now uploaded Mono 4 alpha1, and also KeePass and MonoDevelop 5.7 to my copr account: https://copr.fedoraproject.org/coprs/tpokorra/mono/
Mono4 now even builds for Epel6 and Epel7, by disabling the debug
package.
I am open for suggestions and improvements, and happy to merge pull
requests.
Next steps: So should I go through the list of packages that depend on mono-core in Fedora 22, and rebuild them for Mono4, and people can test them from my copr repo?
This is how I get all packages that somehow depend on Mono: repoquery --whatrequires --recursive mono-core
First off, thank you for doing this work!
I'm completely new to the .Net/C# and Mono universe, but I've been using Fedora (and Redhat before that) for a very long time.
I have recently been assigned the task of migrating a .Net/C# application to Linux, and as such I'm currently using your packages to go through a few of the online C# tutorials :)
I'm *very* interested in seeing a recent (4.0+) version of Mono officially supported in Fedora, as that will have a much better chance of smoothing the migration of applications originally developed on Windows.
I do have some moderate packaging experience (I'm down to three Fedora packages, having orphaned a bunch of stuff I was no longer using professionally).
If I can be of any help (if nothing else, I plan to use your latest packages to learn c#, and generally serve as guinea pig), please let me know.
I wanted to at least start by add a "+1" to the effort of upgrading Fedora's official Mono package set to 4.0.X.
Thanks again, --Gabriel _______________________________________________ mono mailing list mono@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/mono
--
Claudio Rodrigo Pereyra Diaz Ingeniero en Informática
Hello, this is all looking good! Now with Mono 4.0.1 officially released, nothing can stop us now :)
Claudio is doing all the work on the packages, thank you! I wonder if the package owners of the packages depending on Mono will have any work left ;)
On 29 April 2015 at 19:28, Claudio Rodrigo elsupergomez@gmail.com wrote:
Hello.
I fix more and more package to build with mono 4. I will update Change mono 3 proposal for F22 to mono 4 for F23 but I need sponsor for my package https://bugzilla.redhat.com/show_bug.cgi?id=1192059 to became packager and next co maintainer of mono. Some of you can do a formal review of gtk-sharp3 package and sponsor me?
@Xavier: Could you please have a look at this?
Thank you, Timotheus
mono@lists.stg.fedoraproject.org
-
Claudio Rodrigo -
Exile In Paradise -
Gabriel Somlo -
Timotheus Pokorra