From: Nelson H. F. B. <be...@ma...> - 2006-10-19 14:00:43
|
At present, a build of clisp (2.41 being the most recent) produces an installation of 84 files in these directories: $(prefix)/bin/clisp $(prefix)/lib/clisp/ $(prefix)/share/doc/clisp/ This makes it inconvenient to maintain multiple versions of clisp on the system, since the only way to do that is to change the value of prefix, requiring yet another directory in a possibly already-long PATH list. Many other packages take the approach exhibited by this structure: $(prefix)/bin/clisp $(prefix)/bin/clisp-x.y.z $(prefix)/lib/clisp-x.y.z/ $(prefix)/share/doc/clisp-x.y.z/ or this one $(prefix)/bin/clisp $(prefix)/bin/clisp-x.y.z $(prefix)/lib/clisp/clisp-x.y.z/ $(prefix)/share/doc/clisp/clisp-x.y.z/ where the clisp file in the bin directory is a (symbolic or hard) link to clisp-x.y.z. Installation of the next release of the package removes $(prefix)/bin/clisp before installing the new executable, so that on completion, all older versions remain intact, and usable by explicit name, with clisp pointing to the most recent. With large complex systems, I have often found it useful to be able to easily try older versions of the package when an anomaly or bug shows up. Please consider making such a change in future versions of clisp. I also notice that clisp has neither a manual page nor an emacs info document; both would be welcome additions to future distributions. While there are a dozen HTML files in the distribution tree, along with clisp.{dvi,ps,pdf}, Unix systems have no standard place to put these, and users are accustomed to run the man and info commands to find documentation. ------------------------------------------------------------------------------- - Nelson H. F. Beebe Tel: +1 801 581 5254 - - University of Utah FAX: +1 801 581 4148 - - Department of Mathematics, 110 LCB Internet e-mail: be...@ma... - - 155 S 1400 E RM 233 be...@ac... be...@co... - - Salt Lake City, UT 84112-0090, USA URL: http://www.math.utah.edu/~beebe/ - ------------------------------------------------------------------------------- |
From: Sam S. <sd...@po...> - 2006-10-19 15:47:43
|
[oops, posting via gmane does not work!] Sam Steingold wrote: > Nelson H. F. Beebe wrote: >> $(prefix)/bin/clisp >> $(prefix)/bin/clisp-x.y.z >> $(prefix)/lib/clisp/clisp-x.y.z/ >> $(prefix)/share/doc/clisp/clisp-x.y.z/ > > some packages do that. > some don't. > you can try > make install lisplibdir=/usr/lib/clisp-x.y.z > >> Please consider making such a change in future versions of clisp. > > http://www.cygwin.com/acronyms/#PTC > >> I also notice that clisp has neither a manual page nor an emacs info >> document; both would be welcome additions to future distributions. > > this claim is surprising. > clisp comes with a man page in both HTML and ROFF, and "make install" > installs both. > > if you know of a way to generate info from docbook/xml, PTC. > clisp also comes with extensive implementation notes in HTML format > (multi-part: http://clisp.cons.org/impnotes/, monolith: > http://clisp.cons.org/impnotes.html) > > Sam. > |
From: Pascal B. <pj...@in...> - 2006-10-19 22:48:06
|
Nelson H. F. Beebe writes: > At present, a build of clisp (2.41 being the most recent) produces an > installation of 84 files in these directories: >=20 > $(prefix)/bin/clisp > $(prefix)/lib/clisp/ > $(prefix)/share/doc/clisp/ >=20 > This makes it inconvenient to maintain multiple versions of clisp on > the system, since the only way to do that is to change the value of > prefix, requiring yet another directory in a possibly already-long > PATH list. >=20 > Many other packages take the approach exhibited by this structure: >=20 > $(prefix)/bin/clisp > $(prefix)/bin/clisp-x.y.z > $(prefix)/lib/clisp-x.y.z/ > $(prefix)/share/doc/clisp-x.y.z/ >=20 > or this one >=20 > $(prefix)/bin/clisp > $(prefix)/bin/clisp-x.y.z > $(prefix)/lib/clisp/clisp-x.y.z/ > $(prefix)/share/doc/clisp/clisp-x.y.z/ >=20 > where the clisp file in the bin directory is a (symbolic or hard) link > to clisp-x.y.z. >=20 > Installation of the next release of the package removes >=20 > $(prefix)/bin/clisp >=20 > before installing the new executable, so that on completion, all older > versions remain intact, and usable by explicit name, with clisp > pointing to the most recent. >=20 > With large complex systems, I have often found it useful to be able to > easily try older versions of the package when an anomaly or bug shows > up. >=20 > Please consider making such a change in future versions of clisp. What's the problem with a different prefix for each version? I install my compilers in /usr/local/languages/${language}-${version} and make a symlink named /usr/local/languages/${language} on the version I want to use, plus symlinks from /usr/local/bin and possibly from /usr/local/lib and usr/local/man to /usr/local/languages/${language}/* as needed. This allows easy interactive use of the latest version, while the applications in production can use the exact version they're compiled for using the absolute paths like /usr/local/languages/clisp-2.38/bin/cli= sp It would be totally useless to put all of these bin in the PATH, since only the first one could be lauched thru the path. --=20 __Pascal Bourguignon__ http://www.informatimago.com/ PLEASE NOTE: Some quantum physics theories suggest that when the consumer is not directly observing this product, it may cease to exist or will exist only in a vague and undetermined state. |