Mono Adds Mac OS X Package 53
Good news for those of you who've went through the pain of trying to get Mono installed on Mac OS X: the team has quietly added a Mac OS X package. If you previously installed to /usr/local, however, be aware that the packaged version installs to /opt/local and adjust any paths accordingly. The Beta-1 Windows installer has also been fixed; download it here.
Is .Net on OS X a Good Thing? (Score:5, Interesting)
I am sure that others have expressed this view before, but is this necessarily going to be A Good Thing? Isn't this going to lead to developers less likely to have special OS X ports that take advantage of specific OS X features?
Don't mean to be a whiner of course :)
Explanation of /opt/local and /usr/local (Score:1, Interesting)
Re:Explanation of /opt/local and /usr/local (Score:2, Interesting)
Of course, if I was using slackware's 'official' package of Mozilla, it would probably put all the binaries in /usr/bin, all the libraries in /usr/lib and so on. But for downloading and trying out nightly builds or betas, I would always use /opt.
Finally. . .iFolder (Score:4, Interesting)
Re:Aha! (Score:3, Interesting)
By linking proc to ~/proc, you will limit the use of Mono (or whatever is installed in /proc) to one user (unless you duplicate it in every user account). Programs that should be available to all users should NOT be installed in a particular user's directory. That's a terrible practice. If you are so convinced in thinking different(ly), link it to /Users/Share/proc, but then again you have an absolute path.
Whose "utter"?