I'm sorry, I can't, I don't understand it either (nor can I fix it). That's why I keep whining about "scary" changes. One thing that the packages system doesn't cleanly handle is recursive requirements. This results in seemingly "bogus" requirements in various packages, and affects usually the situation when someone is building a single package after a "make distclean autoloads" or "cvs co packages; cd packages; make autoloads". Then if package A requires B, which in turn requires C, we might need to add C to A's requirements even if the code in A has no direct references to anything in C. But the eshell/ecb breakage is something else, I've never seen that stuff before. Hopefully it's fixed by the autoload. -- \/ille Skyttä scop at xemacs.org