On 13 April 2015 at 13:29, Claudio Rodrigo
<elsupergomez(a)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.s...
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!