Hi, On Mon, Oct 10, 2011 at 03:06:24PM +0200, Thomas Mittelstaedt wrote: While we're at it, could you please remind me how to tell ./configure where I want XEmacs to find packages at run time? I'm not installing the built XEmacs, which is at: ~/emacs/xemacs.hg/xemacs. My packages directory, also not installed is at: ~/emacs/xemacs.hg/xemacs-packages. I've tried .... --with-system-packages=~/emacs/xemacs.hg/xemacs-packages --with-system-packages=~/emacs/xemacs.hg --with-package-path=~/emacs/xemacs.hg/xemacs-packages --with-system-packages=~/emacs/xemacs.hg/ --with-system-packages=~/emacs/xemacs.hg/xemacs-packages/ --with-package-path=~/emacs/xemacs.hg/xemacs-packages/xemacs-packages , and perhaps a few more combinations. The result is always the same - XEmacs builds, but at runtime there is nothing in `load-path' pointing at my packages directory. Help, please! -- Alan Mackenzie (Nuremberg, Germany). _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

Hi, Mats. Thanks for the reply. On Mon, Oct 10, 2011 at 07:00:22PM +0200, Mats Lidell wrote: I think I'm sure I've made no typing mistakes. Something wierd is going on. If this configuration element worked, what would I be seeing? Any other suggestions? _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

Mats Lidell <matsl(a)xemacs.org&gt; writes: Also, the output of "xemacs -debug-paths" might help figure out what's going on. -- Cheers =8-} Mike Friede, Völkerverständigung und überhaupt blabla _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

Hi, Mats. On Tue, Oct 11, 2011 at 07:13:26AM +0200, Mats Lidell wrote: Er, yes, that's precisely what I'm doing. This should work, surely? At the moment, there are only .el files in these directories. Will this prevent XEmacs from recognising the directories as `load-path' components? What does "install" mean? It means, primarily, that files get copied to /usr/local/share/.... So why would /usr/local/share/.... work, but my source directory not? I'll try compiling all the packages and see if that makes a difference. -- Alan Mackenzie (Nuremberg, Germany). _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

Hi, Mats. On Tue, Oct 11, 2011 at 03:56:03PM +0200, Mats Lidell wrote: <sigh> I'm part way there. I'm getting an error [2] from make. I'll get it sorted out sometime. Presumably after each little change to my (package-)source code, I'll need to do a 'make install' to test it. Or would it be better to put the source code directly under the install directory? This is a real time sink, for both of us. Thanks for the help. -- Alan Mackenzie (Nuremberg, Germany). _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

Hi, Mats On Tue, Oct 11, 2011 at 05:57:19PM +0200, Mats Lidell wrote: OK. I've got my Local.rules file set up. I did it first by building the packages (which takes long enough), then experimenting with XEmacs ./configure settings until something worked. This seems a bit backwards, but it worked. Does that really mean a /src directory at the top level of the file system? I put ~/emacs/xemacs.hg/xemacs-packages.elc into XEMACS_INSTALLED_PACKAGES_ROOT, but I had to go one level down when specifying --with-package-path=... in the ./configure file. Ah well, I've got it now. Now to get on with the real work. ;-) -- Alan Mackenzie (Nuremberg, Germany). _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

Andreas Röhler writes: Just like curing the cold, it's as simple as "Take two aspirin and call me in the morning." If you think you need it, you're probably thinking too much. It's just ./configure --prefix=$PREFIX --with-system-packages=$PATH_TO_INSTALLED_PACKAGES make make install # you may need su or sudo --prefix may be omitted if the default of /usr/local is appropriate, and --with-system-packages may be omitted if the default of $prefix/share/xemacs is appropriate. ($PATH_TO_INSTALLED_PACKAGES should contain xemacs-packages and possibly mule-packages and/or site-packages.) The only tricky thing about it is that the packages *must* be in installed format (there is a way to create a symlink farm instead of physical copies, but I don't know if that really makes sense); you can't use packages in the source tree. (This is admittedly stupid, but only Mike knows enough about the package system to do something about it in the near future and he doesn't seem interested.) The easiest way to install packages is cd /tmp # NOTE NOTE NOTE: the host is FTP.xemacs.org, not WWW.xemacs.org # There's also a .bz2 which saves about 25% bandwidth. wget http://ftp.xemacs.org/packages/xemacs-sumo.tar.gz cd $PATH_TO_INSTALLED_PACKAGES tar xzf /tmp/xemacs-sumo.tar.gz To work on packages you do need a package source tree, of course. But that's a different thread. All of this is documented in excruciating detail in man/beta.texi, or if you have a working Info reader, you can cd to man, do make beta.info, and read it more pleasantly. No, I see no point in adding more documentation. beta.texi is the appropriate place, this *is* a beta distribution. The next public release of XEmacs *will* build and install with the above instructions, and the various feature options are documented in ./configure --help. I also hope to make package bootstrapping somewhat more self-contained (but that's a different thread, too). _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

"Stephen J. Turnbull" <stephen(a)xemacs.org&gt; writes: It just never occurred to me, as running-only-from-installed was deeply built into the package system from the start. But it shouldn't be hard to do - the trick is probably finding out whether you're looking at a source hierarchy or an installed hierarchy: I'll put it on my list. -- Cheers =8-} Mike Friede, Völkerverständigung und überhaupt blabla _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

"Stephen J. Turnbull" <stephen(a)xemacs.org&gt; writes: Yeah, but the whole path-searching code was built without a fixed assumption as to tree depth, so I believe it can cope. If you can define the tree layout, you can also get the paths. Do you have a pointer? Back then, I did quite a bit of work on that aspect, and I couldn't any way to do with less. -- Cheers =8-} Mike Friede, Völkerverständigung und überhaupt blabla _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

"Stephen J. Turnbull" <stephen(a)xemacs.org&gt; writes: We discussed caching the load-path way back; I really dislike that idea, and see even more bug reports coming because that cache is out of synch. Is there really still that much of a problem? -- Cheers =8-} Mike Friede, Völkerverständigung und überhaupt blabla _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta