Proposed change to ghc installation procedures

Greetings, GHC users. If you install GHC from .rpm's, Debian .deb's, InstallShields, or other package formats, READ NO FURTHER. The following DOES NOT AFFECT YOU. The following applies ONLY if you install GHC from binary .tar.gz files. (Sparc-solaris users might, for example). As the GHC 5 release approaches, we're considering changing how binary builds of GHC are installed. The main aim of this proposal is to simplify parts of the GHC build system which have gotten a bit out of hand and are proving difficult to maintain as a result. The purpose of this message is to show the proposed changes and find out if it will cause problems for people. Up till now, the installation procedure (eg with 4.08.2) was gzip -dc ghc-4.08.2-my-platform-descriptor.tar.gz | tar xvf - cd ghc-4.08.2 ./configure --prefix=/where/ghc/should/be/installed make install The proposed new installation scheme is in fact a return to an old scheme: gzip -dc ghc-4.08.2-my-platform-descriptor.tar.gz | tar xvf - and then edit by hand ghc-4.08.2/bin/my-platform-descriptor/ghc5 to set the GHC_TOPDIR env variable to point to the top of the installation tree. So you run the distributed image in-place. The initial edit of the ghc5 script allows it to know where it is installed. This simplifies our build process; no longer do we need to create an installation-time Makefile or configure script and all its supporting junk. I assume that most users install from .rpms, so this change only affects package builders and sparc-solaris users. Please eeeep ASAP if this will cause you problems; otherwise we will go ahead with it in in the next couple of days. J

On Tue, 20 Mar 2001, Julian Seward (Intl Vendor) wrote:
edit by hand ghc-4.08.2/bin/my-platform-descriptor/ghc5 to set the GHC_TOPDIR env variable to point to the top of the installation tree.
I guess it will have a reasonable default (/usr/local/lib/ghc-5.00) and tell the user to edit the file in case ghc is not found there? -- Marcin 'Qrczak' Kowalczyk

"Julian Seward (Intl Vendor)"
The purpose of this message is to show the proposed changes and find out if it will cause problems for people. Up till now, the installation procedure (eg with 4.08.2) was
gzip -dc ghc-4.08.2-my-platform-descriptor.tar.gz | tar xvf - cd ghc-4.08.2 ./configure --prefix=/where/ghc/should/be/installed make install
The proposed new installation scheme is in fact a return to an old scheme:
gzip -dc ghc-4.08.2-my-platform-descriptor.tar.gz | tar xvf - and then edit by hand ghc-4.08.2/bin/my-platform-descriptor/ghc5 to set the GHC_TOPDIR env variable to point to the top of the installation tree.
So you run the distributed image in-place. The initial edit of the ghc5 script allows it to know where it is installed.
I think, this is great, because then we can finally have relocatable rpms. So, people without root access can install from rpm. How about providing a script `settop' that given a directory path does the editing of ghc-4.08.2/bin/my-platform-descriptor/ghc5 (This would be exactly what is required as a post install script for a relocatable rpm and might be convenient for manual installation, too.) Manuel
participants (3)
-
Julian Seward (Intl Vendor)
-
Manuel M. T. Chakravarty
-
Marcin 'Qrczak' Kowalczyk