This ebuild builds the presntly latest available mcs-version (0.16), the Mono Class Libraries and C# Compiler. Mono is an open source implementation of the .NET Development Framework. It includes a compiler for the C# language, a runtime for the Common Language Infrastructure (CLR) and a set of class libraries. http://www.go-mono.org We wrote this eBuild, because there exists no corresponding eBuild. Because there exists no intependent subtree we called it dev-lang/mcs
Created attachment 4485 [details] mcs-0.16.ebuild
Hi, this ebuild installs a subset of files that dev-lang/mono installs, and this ebuild lists mono as a dependency, so I don't really see the point of this ebuild. Can you explain? After this ebuild is installed, the 'mcs' script still points to /usr/bin/mcs.exe installed by mono, while this ebuild installs a /bin/mcs.exe. A believe that means the files installed by this ebuild would not even be used.
Hi! I controlled it, and you're right. But for my defense: The main goal for this ebuild were the additional class libraries for mono. And it needs mono because it use the msc as compiler. And it build another version of the msc for demonstrating that it can compile itself, which is - as i know - a major step for a compiler. And now something distressing: we haven't noticed, that the msc was installed :-[. Perhaps this could happen, because we awaited to much of mono, so that our interest is not as great as it was a few months ago. But however: with mono 0.17 this ebuild and its problems are not longer important resp. up to date. Tim
Closing this bug, thanks for your effort.
