The maintainer is busy in real life. Is the update a simple pkgver bump? Then I could do this for you.
Thank you very much for the update. I used it and for me it seems to work flawlessly.
]]>On a side note, I ran into issues debugging an old asp.net mvc project after the upgrade, where xsp would not launch and I could not debug. I was having the same issues when running the project in monodevelop built from source, so I don't think there's anything the arch devs could do. Just in case someone else runs into this problem, it seems that deleting the .userprefs file for the solution fixes the issue and allows xsp to launch again.
]]>The maintainer is busy in real life. Is the update a simple pkgver bump? Then I could do this for you.
Seems to work. I don't actually use monodevelop so I can't confirm anything more than it gets packaged and it runs.
]]>Did the maintainer ever get back to you on this?
Not yet. I am waiting for it and will post his answer here.
]]>So I will ask the maintainer directly and post his reply here.
]]>Does anyone know why the monodevelop package does not get updated? It was flagged out of date in May and should currently be version 3.0.3. There are also some cool new features that seem quite helpful for developing with C#.
This might be a stupid question but I don't know where to find the reasoning for the decision to keep monodevelop on 2.8. Is there some general place where package upgrades are discussed?
Looking forward for the update ;)
Thomas.