Hi Sebastian,
Ok, now that etch is release what shall we do about this bug, Anuradha? Does your upstream consider to change the name of the binary?
Sorry for the late response, but I've been a bit busy lately and I've not had much time for anything else. But things should change soon, hopefully. The last time I spoke to Stelios, he was not completely for changing the ncc binary name. According to his view, which I tend to agree with, he believes nemerle should rename it's ncc binary to something that's more appropriate for a dot-net application, such as with an .exe suffix. But according to the CLI Policy [1] "Never ever install application files (.exe) directly into /usr/bin. Instead create a wrapper script into /usr/bin to allow them to be run without the .exe suffix." So I'm guessing that would not work? Forgive my ignorance on the CLI policy, but do you know if it is an approved policy document? I realize this can be a stale mate situation, and I'm not clear what nemerle's stance on this issue is and whether they would consent to a name change. Any suggestions? [1] - http://pkg-mono.alioth.debian.org/cli-policy/ch-packaging.html -- Anuradha Weeraman http://www.linux.lk/~anu/ http://anuradha.wordpress.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
