Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=460304
--- Comment #13 from Tom Moertel <tom(a)moertel.com> 2008-09-04 23:44:39 EDT ---
Yaakov, thanks for explaining your concerns in detail.
In reviewing Jens's spec for ghc-X11, it appears that it avoids your primary
concern by passing the "--ghc" flag during the initial Cabal-setup invocation:
%build
%cabal_configure -p --ghc <= HERE
%cabal_makefile
%cabal build
%cabal haddock
%ghc_gen_scripts
According to the Cabal documentation, this flag ensures that Cabal will use GHC
for the later stages of Cabal processing, regardless of which Haskell
implementation runhaskell invokes. (Ref:
http://www.haskell.org/ghc/docs/latest/html/Cabal/builders.html#setup-con...)
So even if runhaskell invoked NHC, for example, Jens's spec would still build
a GHC package.
Do you think using Cabal-setup flags to specify the desired compiler will
adequately resolve your concern about hidden compiler dependencies?
Cheers,
Tom
--
Configure bugmail:
https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.