Adding --package-path=/where/your/packages/are to the usual configure
command should make things work. I imagine Mike Sperber has mentioned
that already. I'm not going to push any farther at this point,
because the "uniform path searching" Mike describes really has been a
big win, and the workaround simply is not that painful. (Right?)
I believe there _is_ a natural notion of "package root", but I can't
specify it yet. Since Mike doesn't want to go there at this point,
it's going to have to wait until the FAQs convince him otherwise ;-)
or somebody comes up with a spec that convinces him.
Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Don't ask how you can "do" free software business;
ask what your business can "do for" free software.