On Thu, 23 Apr 2009 20:47:10 +0200 Michael Biebl <[email protected]> wrote:
> Mirco Bauer wrote: > > The main purpose of mono-devel is to provide the default CLI > > development stack, which isn't 1.0 anymore (since the Mono 2.0 > > transition), and gmcs is not broken at all, thus downgraded to > > important. > > > > So /usr/bin/mcs is a left-over which has not correctly been removed > when mono-devel was upgraded from 1.0 to 2.0? To be precise, mono-devel didn't exist before (the package was in sarge but not for the default stack purpose). We (re)-introduced this package so all source packages can use a common buid-dependecy making sure the current default stack is pulled in. When we moved files around, some files hit mono-devel that shouldn't (e.g. mcs, as that targets explicitly 1.0). > > One of the reasons, why I noticed/filed this bug is, that a software > I maintain, checks for /usr/bin/mcs in ./configure, and if it finds > that, it enables a mono addin. Obviously the build fails later on. It should not check only for mcs, good practice is to check for: csc, gmcs, mcs (in that order), that ensures you get the best C# compiler available. Unfortunately csc is only available on Debian and no other linux distros (well besides ubuntu as they use our packages). Upstream has no official version neutral default compiler (which Microsoft has: csc). I hope this could clear this situation a bit, for some more background information see: http://wiki.debian.org/Teams/DebianMonoGroup/Mono20Transition > > Michael > -- Regards, Mirco 'meebey' Bauer PGP-Key ID: 0xEEF946C8 FOSS Developer [email protected] http://www.meebey.net/ PEAR Developer [email protected] http://pear.php.net/ Debian Developer [email protected] http://www.debian.org/ -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
