hscolour is an application to add color to haskell source code, generating html files. It can work together with the documentation tool dev-haskell/haddock, to color any code haddock generates documentation for. The updated eclass haskell-cabal allows to colour any source code if we in the ebuild have defined CABAL_FEATURES="hscolour" and the user has enabled USE="hscolour". So far no ebuilds in portage has this definition, but we plan is to add it for all new ebuilds. So, dev-haskell/hscolour will be a dependency to many packages. Luckily it's well tested, and the change to the eclass has already been used close to one year in the haskell overlay. From the following arches we need to mark dev-haskell/hscolour stable: * alpha * amd64 * ia64 * sparc * x86 And from these arches we need ~keywording: * ppc * x86-fbsd
x86 stable you probably want prefix or gentoo/freebsd team for x86-fbsd
Thanks Paweł!
Sorry * QA Notice: Files built without respecting LDFLAGS have been detected * Please include the following list of files in your report: * /usr/bin/HsColour
(In reply to comment #3) > Sorry > > * QA Notice: Files built without respecting LDFLAGS have been detected > * Please include the following list of files in your report: > * /usr/bin/HsColour I presume it's an amd64. How did you detect it? With '-Wl,--hash-style=gnu' one? I'd also like to hear from you how you did install ghc (as it's he who generates binary pieces and calls ld to link them). Thanks!
(In reply to comment #4) > (In reply to comment #3) > > Sorry > > > > * QA Notice: Files built without respecting LDFLAGS have been detected > > * Please include the following list of files in your report: > > * /usr/bin/HsColour > > I presume it's an amd64. > > How did you detect it? With '-Wl,--hash-style=gnu' one? I'd also like to hear > from you how you did install ghc (as it's he who generates binary pieces and > calls ld to link them). > > Thanks! > Yes on amd64 using -Wl,--hash-style=gnu. here is the output of emerge -pv ghc Calculating dependencies ... done! [ebuild R ] dev-lang/ghc-6.8.2-r1 USE="-bash-completion -doc -ghcbootstrap" 38,953 kB
> Yes on amd64 using -Wl,--hash-style=gnu. > > here is the output of emerge -pv ghc > > Calculating dependencies ... done! > [ebuild R ] dev-lang/ghc-6.8.2-r1 USE="-bash-completion -doc > -ghcbootstrap" 38,953 kB > May I ask you and others to disregard this issue and keyword it stable? LDFLAGS ignorance is not personal hscolour's fault, but rather Cabal's-the-library (which is used when building most of haskell packages, thus they have the same disease, but *shh*). Similar upstream bug: http://hackage.haskell.org/trac/hackage/ticket/458
Yeah fair enough At least upstream is aware of that amd64 done Could you please open a bug and make it block bug #331933 so we know which packages don't respect LDFLAGS
> amd64 done Thanks! > Could you please open a bug and make it block bug #331933 so we know which > packages don't respect LDFLAGS done: bug #333217
alpha stable
ia64 stable sparc removed. Current stable ghc on sparc requires gcc:4.1 to work. I propose to stabilize hscolour later right after ghc-6.10+ stabilization (not tied to gcc).
Adding sparc back for stable request queue (it has stable ghc-6.12.3 now).
sparc stable
ppc/ppc64 stable
x86-fbsd done by naota: > 13 Oct 2011; Naohiro Aota <naota@gentoo.org> hscolour-1.17.ebuild: > Add ~x86-fbsd Closing. Thanks guys!
