Confusion surrounding CVS xemacs-packages usability

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I am trying to keep a hierarchy of XEmacs/xemacs-packages CVS updated and usable for the xemacs binaries installed. However, I am thoroughly confused about how to set this up without using symbolic links and long EMACSLOADPATH's. When I drop the SUMO xemacs packages (and mule packages) into the appropriate directory, then xemacs is easily able to find any and all packages. The layout of the directories that the two tar files (sumo packages and sumo mule) creates is: {xemacs,mule}-packages/{etc,info,lib-src,lisp,man,pkginfo}. However, when doing a CVS update of XEmacs/xemacs-packages, the layout is considerably different. I place the CVS hierarchy in /usr/local/src/XEmacs/XEmacs/xemacs-packages. Now because xemacs is not going to look here unless directed to by the load-path, I need to make this available to users automatically--perhaps through a single symbolic link. My initial approach was to, from /usr/local/lib/xemacs-21.2-b26: ln -s ../../src/XEmacs/XEmacs/xemacs-packages . and ln -s ../../src/XEmacs/XEmacs/xemacs-packages/mule ./mule-packages However this approach fails. I could consider populating the directory with mysterious symbolic links so that the two layouts appear to be the same, but this does not seem to be the best approach and would even be hard to automate because there are exceptions in the layout of the tree that would have to be dealt with manually. Clearly untarring the SUMO packages works without any additional effort. However there seems to be no way to do the same for the checked out CVS xemacs-packages tree. My first step after doing the CVS update is to do a ``make World'' from that directory (which completed successfully). Initially I thought that this would take care of presenting the available packages to XEmacs automatically, but this was not the case. The advantage of using CVS is the speed of doing a CVS update rather than fetching a new SUMO tar file or even fetching newer packages one by one. From having a checked out CVS xemacs-packages tree and an xemacs-21.2-b26 base install (with defaults), what is the quickest and most elegant way to present the former to the latter so that all packages are available? Any help on this matter would be greatly appreciated. Michael Lee Crogan -- <mcrogan(a)purdue.edu&gt; -- Purdue University