hackage.haskell.org doesn't have the latest version 1.6.4

[yurivict]

here

[alex-mckenna]

The packages clash, clash-vhdl, clash-verilog, and clash-systemverilog on Hackage are not the currently maintained / released packages. At some point the clash-HDL packages were folded into clash-lib, and clash was deprecated in favour of clash-ghc.

Maybe we should consider removing these old packages, or at least make sure the clash-HDL ones mentioned they are deprecated in favour of clash-lib (a similar warning is in the contents of clash on Hackage)

[yurivict]

So if I would like to create FreeBSD ports for clash - should there be just one port clash-ghc?
Does it build one executable and this is all that is needed?

[alex-mckenna]

You would want to package I think at minimum clash-prelude for the standard library, clash-lib for the compiler-as-a-library and clash-ghc for the GHC frontend (with clash and clashi executables). You may also need to package the typechecker plugins: ghc-tcplugins-extra, ghc-typelits-extra, ghc-typelits-knownnat, ghc-typelits-natnormalise since they are runtime dependencies of clash-ghc

[martijnbastiaan]

The only thing you should need for Clash to work on FreeBSD would be for GHC/Cabal to work. It does not look like GHC officially supports FreeBSD though. Apart from that I don't think Clash does any OS-specific things.

[alex-mckenna]

It shouldn't be the most difficult thing to get FreeBSD support though, since ghc used to support it but dropped it a few versions ago for some reason

[yurivict]

It does not look like haskell/ghcup-hs#834 (comment) though.

ghc works fine on FreeBSD though. We have many Haskell-based ports.

[alex-mckenna]

I think we should mark clash-vhdl, clash-verilog and clash-systemverilog as deprecated on Hackage (as we have with clash) so this confusion doesn't happen again. Other than that there isn't really anything to do for this issue.

@martijnbastiaan Would you mind, since you have permission

[martijnbastiaan]

Done!