New JDE version [WAS: Test release of new packages]

ms> I now realize why I never saw the problems you're seeing: The ms> macro causing the defect is Win32-specfic. Anyways, I've Not all of them; I'm seeing problems on Linux, too. It is probable that the important reason you never saw the problems we are seeing is that you built the package in the context of (a) an otherwise up-to-date *installed* package hierarchy and possibly (b) with compiled .elcs in place in the *source* hierarchy. My installed hierachy is about 3 months old; my CVS is a fresh update. That's probably the source of some of the problems I'm seeing. This really is a problem with the design of the package building process, you know. (Actually, it's just undocumented; if you look at how Steve handled this problem, he always puts in the necessary PRELOADS and load-path updates so that the _source_ package hierarchy is preferred.) ms> (hopefully) added the necessary compile-time directives, and ms> backed out the PRELOADS patch to Makefile, and bumped up the ms> package version. Let me know if there are any more problems. I guarantee you that it is _not_ possible to bootstrap JDE from CVS only without the load-path augmentation that was in the PRELOADS variable. You will have to build and install the semantic and speedbar packages first. I believe that will work in this case, but it won't always work. (Of course it is _possible_ to do the necessary work purely in Lisp, but this will introduce strong XEmacs dependecies in the Lisp library, which are unnecessary since we have settled on make as the tool for maintaining the package hierarchy. Why not take advantage of that and localize these XEmacs dependencies to the Makefiles?) In any case, it will be the source of future bug reports in situations like this unless we systematize building packages in a process which ignores any installed package hierarchy. -- University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091 _________________ _________________ _________________ _________________ What are those straight lines for? "XEmacs rules."