It's been awhile since I've talked with you ... hope things are well with you all. I have been lurking in the shadows, watching orange's development ... and I must continue to say ... well done!

Anyone, on to business, for the linux build there are at least three bugs right now:

1) When you run setup.py, the binary files need to be recompiled. This has two sub issues. First, the source code snapshot probably shouldn't include any binaries (so the make files won't find them and hence, they will be built). Second, even if the binaries are present, they should probably be rebuilt.

The second part of the problem is that the source needed to produce orngCRS.pyd (or orngCRS.so) is not included in the snapshot (if it is, I missed it ... sorry!).

3) Finally, the way that the "system wide" install directly sets links in /usr/lib is incompatible with some package distribution systems (for example, Gentoo). Everything else is better b/c it is done relative to some root. However, the linking is done with absolute pathnames and this causes a problem.

Not sure if this will help or not, but here's the setup.py file I made while working on making a Gentoo package for orange. It doesn't handle the "uninstall" case, but it is quite a bit shorter and doesn't do the "rogue linking". It was based off of Tomaz and Jure's original setup.py (from the Oct 3 snapshot).

## these don't account for any input parameters like --root --prefix --home, etc## actually, as long as they are not absolute, they will account for other# factors, but it is not well documented __HOW__ they will accout for them# *** distutils needs better docs!#OrangeInstallDir = os.path.join("lib", PythonVer, "site-packages", "orange")OrangeInstallDoc = os.path.join("share", "doc","orange")OrangeInstallLib = os.path.join("lib")

For completeness (and since I'm in the middle of finishing my dissertation writing and I have limited time to spend on this .... have at it someone else!), here's the ebuild file that went with that setup.py command.

It seems that the orng-snapshot is built with a more recent version of orngExtn (and hence a newer orngCRS). Getting the newer source for orngExtn distributed with orng-snapshot would be a good idea. As it stands, building orngCRS with the older orngExtn requires deleting the various *.py files that are part of orngExtn and included in orng-snapshot and replace them with equivalent the old orngExtn files.