Hi ports@, Attached is a new port: devel/hs-ShellCheck, a shell script analysis tool. It depends on textproc/hs-json for which I just sent a new port because it is not in the ports tree yet.
This port provides both a utility (bin/shellcheck), and a Haskell library. Should I split up the port into -main and -lib subpackages, just like x11/xmonad? Another approach is to let the user use cabal to get the library, and not install the library at all. Depending on that, maybe the port should be renamed from hs-ShellCheck to just ShellCheck or shellcheck. The port doesn't build on i386 for the same reason devel/hs-fgl fails so (at least for now) the port is marked BROKEN-i386. I'd like to know whether anyone is interested in this port. And of course, feedback is appreciated. Thanks, Caspar Schutijser $ cat pkg/DESCR ShellCheck is a shell script static analysis tool. The goals of ShellCheck are: * To point out and clarify typical beginner's syntax issues, that causes a shell to give cryptic error messages. * To point out and clarify typical intermediate level semantic problems, that causes a shell to behave strangely and counter-intuitively. * To point out subtle caveats, corner cases and pitfalls, that may cause an advanced user's otherwise working script to fail under future circumstances.
hs-ShellCheck.tgz
Description: application/gtar-compressed
