Re: [MERGED-BEN-MULE] mule doesn't compile on linux

Ben> anyway, there is more than one possible path to take. the Ben> one i'm taking is to disable entirely all recognition of Ben> packages when compiling xemacs. I agree with this. Ben> this requires another command-line flag -- no-autoloads isn't Ben> enough because the shadowing file still sits on the load path. I'm not sure I want to add yet another command-line flag, though. We have too many as it is. My current approach is to add -l lisp/autoloads \ -eval "(setq load-path '(\"`pwd`/lisp/\" \"`pwd`\"/lisp/mule/\"))" to the action in the rule where it matters, but I think the best thing to do would be to create a file buck-naked-build-environment.el and always load it with -l. I'll submit a patch for the current approach for your perusal and the use of people with mule-ucs installed. Ben> my only concern is people adding other stuff to dump, which Ben> is dependent on packages. is this a real concern IMO, yes. We should support this somehow. Ben> that i should worry about? Not yet, unless you want to. It's poorly supported now, and we would need to find a way to do it cleanly. If they really want to do that, they should set it up explicitly with a just-get-my-packages-environment.el. We could put instructions in our version (";;; to preload packages, add them to load-path here" etc etc) and rename buck-naked to clean-build-environment.el. -- 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.