On Fri, Mar 16, 2007 at 12:12:49PM +0000, Malcolm Wallace wrote:
> Sven Panne <[EMAIL PROTECTED]> wrote:
>
> > but they should *not* install these tools
> > along with the compiler/interpreter in question.
>
> However, nhc98 won't mind in the slightest if somebody else installs
> cpphs as well, or over the top of its own
nhc98 might not mind, but package managers like dpkg/apt get upset if
two packages both want to install /usr/bin/cpphs.
One way would be for nhc98 to install something like /usr/lib/nhc98/cpphs
so that if a cpphs package installs /usr/bin/cpphs there is no conflict.
nhc98 would probably always call /usr/lib/nhc98/cpphs even if
/usr/bin/cpphs also exists.
Alternatively, nhc98 could just not install cpphs and complain loudly if
it tries to run it and finds it isn't there (or fall back to plain old
cpp).
I suspect you will prefer the former and Sven the latter :-)
> The installation process for nhc98 could even refuse to
> overwrite a pre-existing cpphs, if that were desirable.
After:
install cpphs
install nhc98
remove cpphs
you end up with an nhc98 and no cpphs.
Thanks
Ian
_______________________________________________
Cvs-ghc mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/cvs-ghc
