Roman Neuhauser <[EMAIL PROTECTED]> writes: >> The packaged installations like RPM and *BSD ports get around this >> by installing the TMDA modules directly into Python's sys.path >> (e.g, /usr/local/lib/python2.2/site-packages/TMDA/). > > why does TMDA itself not do it this way?
Because upgrading/downgrading Python would break the TMDA installation. Python provides a system called `distutils' that manages the installation of custom modules, but unfortunately it provides no way to un-install, and has no concept of dependencies. I'm not sure what the problem is, as the current installation methods seem fine to me. If your OS supports a TMDA package/port/RPM (which covers most users) you are fine. If not, just unpack the TMDA tarball into a src directory, and symlink the bin/tmda-* programs into /usr/bin or /usr/local/bin. _____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
