Simon Marlow wrote:
> I think on reflection that /usr/local/lib/ghc or
> /usr/local/lib/ghc-4.06 would be a better choice than
> /usr/local/lib.
Just a few remarks and personal opinions from a RPM builder's view:
* IMHO the whole /usr/local hierarchy is completely obsolete for
and "real" programs should only be used for quick local hacks.
=> GHC should reside under /usr/{bin,lib,include}
* Using the file system as a DB and coding the version number
into the installation path is not good, either. If look at
existing Linux distributions closely, there is complete chaos
in this respect: Version numbers are often used below the
/usr/lib hierarchy, but not below /usr/bin or /usr/doc, so
there will be collisions from different versions anyway. Any
modern OS should have a decent package concept (RPM for Linux
and some other platforms, Solaris has its own package system
AFAIK), so this is mainly a non-problem.
* Most "normal" users of GHC (are there any ;-) are more than
happy if they get *one* version installed and running. And
power users can easily tweak GHC to reside everywhere they
like, anyway.
> In fact, binary distributions already use the latter.
Not mine, for the reasons above.
> Include files, on the other hand, should really be in
> /usr/local/include/ghc, so f.e. #include <ghc/RtsAPI.h> has a
> chance of working. [...]
sed ,/local,,g :-)
Cheers,
Sven
--
Sven Panne Tel.: +49/89/2178-2235
LMU, Institut fuer Informatik FAX : +49/89/2178-2211
LFE Programmier- und Modellierungssprachen Oettingenstr. 67
mailto:[EMAIL PROTECTED] D-80538 Muenchen
http://www.informatik.uni-muenchen.de/~Sven.Panne
