Re: XEmacs-Beta Digest, Vol 74, Issue 9

steven> Stephen, steven> You mentioned you would be interested in small Install How-To's, steven> So I am offering one based on my recent install. steven> I'm sure there are errors and misspellings, feel free to correct steven> or ask me to correct. Same to anyone else. steven> User-Contributed Installation How-To: steven> xemacs-21.5.32 on Slackware64 14.0 steven> 11/8/2012 steven> user: Steven Mitchell steven> These are the 17 steps taken to install xemacs-21.5.32.tar.gz steven> for all users, on a slackware64 14.0 installation: Ray> 17 steps seems overly complicated. A lot of this depends on which operating system you are installing on. My wife installed on a win7 machine next to me, and downloaded 1 file, ran it, chose packages on the menu, and it installed and she was dome. So for that case, 1 file, and you are through! definitely less complicated. Keep in mind the install-case I am trying to document is for Skackware64 14.0 and not every other case. The INSTALL file Stephen pointed out to me gave general directions suitable for lots of install-cases. Which steps do you think can be eliminated? steven> 2. as root, copy the file xemacs-21.5.32.tar.gz from where ever steven> you downloaded it, to /usr/src with a command like this: steven> cp/home/steve/Downloads/xemacs-21.5.32.tar.gz /usr/src/ steven> verify: ls /usr/src steven> and look to see if the file you copied is there. steven> If your distribution of linux doesn't have a /usr/src directory, steven> create it with this command before copying the above file to it: steven> mkdir -p /usr/src Ray> I never build xemacs as root and instead just build it as myself. I Ray> used to build and install on a server for lots of people to use. This was Ray> never a problem, as long as I remembered to make the directories Ray> readable/searchable. I think a couple of steps do need to be root, like make and make install. The rest of the steps don't need to be done as root as far as I know. This may be some fuzz in my directions as I had them create a directory and was not clear in my own mind if it would be created as root w/root permissions, so for the copying, I said to be root, though that is not strictly needed, if you have the directory permissions set accordingly. Can you tell me 2 things, if you remember them: Which directories did you make readable/searchable? How did you make them readable/searchable? Was it just using chmod? And thirdly, after what step did you make them readable/searchable? steven> 6. Choosing command line options for ./configure. steven> There are many command line options you can set. Almost everyone steven> will have steven> at least some options to specify and almost nobody will be able to steven> install steven> XEmacs without specifying some options. Ray> Isn't this supposed to work without options? Granted the default Ray> installation directory is probably wrong, but xemacs should build and Ray> work. Nowadays, all I specify is --prefix, --with-mule, and Ray> --with-xft, and the latter two are only because I want mule and xft Ray> support. I've tried just running ./configure with no options specified 2 times, once with 21.5.29 and once with an older version, maybe 21.5.24?, and both times I got an installation that did not work right. I'd have to do it again to report the exact problems I got. I can do that if someone truly wants to know, but in my experience I have not been successful in just running ./configure with no options at all on a slackware linux system. I documented the exact external libraries I wanted to use in my ./configure line, but since noticed that a couple of the ones I specified were actually defaults and I could have left them off my ./configure line. steven> 9. To bootstrap the packaging system, download 2 files: Ray> I also never go hunting around for the packages and just grab the Ray> xemacs and mule sumo tarballs. If you're new to xemacs, this is much Ray> easier. I read on the XEmacs web site (I think that was where it was) that the sumo tarballs were not going to be supported on all platforms that you can install XEmacs on. What I don't want to have happen is the new-installer get to this point and look for a suitable tarball and be frustrated when he cannot find it. It could be that the info on the web site is out of date, And tarballs are available for all systems now, in both mule and non-mule flavors. Can anyone tell me for sure if tarballs are currently, and will continue to be, available for all platforms and mule/non-mule versions of XEmacs? Another point about choosing to install the tarballs, is that assumes you want every package installed. I typically don't install every package possible. I never use any form of IRC and don't access email from XEmacs so don't install those packages. Despite living in Germany a few years as a child, I do everything in the English language and cannot read any other language, so don't see the use of having mule installed. Not promoting English over any other language, just saying it does no good for *me* to have it installed. So I go non-mule. Make a case that mule is better for me to have, and I will probably install it. I can modify the instructions to show how to use the mule or non-mule sumo tarballs, then people could choose to do it that way if they want to. Ray, can you give me exact directions to install the sumo tarballs? exact commands and paths you used? where are sumo-tarballs located? If it has been a while, can you give me approximate commands and I will reinstall to try it out. Thanks, Steven Mitchell _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta