Downloading MIEN
Mien can be downloaded from several sources:
Web repository at Montana State University. These repositories also include extension blocks. The MIEN Core (main project) is in the sub-directory named core.
http://mien.msu.montana.edu/repository/dev (development code)
http://mien.msu.montana.edu/repository/stable (code with at least 5 minutes of testing :)
Subversion access
svn co http://mien.msu.montana.edu/svn/mien/mien for the core code (without branches and tags)
svn export http://mien.msu.montana.edu/svn/mien/mien to get the same code as above without version control information (this should be exactly the same as the development web repository)
svn co http://mien.msu.montana.edu/svn/mienblocks to get a bunch of extension blocks
Sourceforge Downloads (Warning: these are probably way out of date)
A Note about the svn repository
Typically, a subversion repository has toplevel directories named "tags", "branches", and "trunk" (or maybe "main"). The MIEN repository is set up like this also, but the "trunk" directory is actually named "mien". This mean that if you do the following:
you will get a directory $HOME/mien/mien. The name of the top level mien command will be $HOME/mien/mien/frontends/mien.
At that point, like my coworkers, you may say YUCK! Why??
Well, I agree that it is rather ugly, but it has the advantage that the mien Python package can be imported directly from a subversion working copy. The name of the directory defines the name of the Python package, so if it was named "trunk", mien couldn't run directly from the svn working copy, which is how I like to run it in my day-to-day work. If you want to do this too, you could set your PYTHONPATH to include $HOME/mien. Then you can import module mien from $HOME/mien/mien/__init__.py
If you aren't developing MIEN, it is probably more convenient to use one of the svn commands listed above. These will extract only the "mien" (aka "trunk") subdirectory, which can be used directly as a Python package.