Hi Greg, On Fri, Apr 02, 2021 at 10:50:05PM -0700, Greg Steuck wrote: > Greg Steuck <gne...@openbsd.org> writes: > > > Updated version in the tarball. I improved the generator upstream and > > added a MESSAGE file. > > Any thoughts on the port? I changed the version number to include the > date as we do in other places like x11/xsel. > > I don't really have a strong reason to keep this port in-tree unless > other people want to add/upgrade Haskell binary ports.
I'm a bit late but yes, I think it would be nice to have this in ports. Last week I was looking at updating the devel/shellcheck port (which, thanks to your work, is a feasible task now) and I came across cabal-module(5) where cabal-bundler is mentioned for the generation of the contents of MODCABAL_MANIFEST. Regarding pkg/MESSAGE: would it perhaps make sense to make it a pkg-readme? I have no doubt I will forget about running cabal v2-update at some point and as a pkg-readme, I'll have a way to find it back later. I guess whether my suggestion makes sense depends on whether cabal v2-update should be rerun every now and then to keep the hackage package list updated; my assumption is that that is necessary. Is that correct? I tried to use this for ShellCheck but that fails (see below). Still need to have a closer look at that. Regardless: tested it on amd64 (with some hackage packages other than ShellCheck) and it works fine here. Thanks, Caspar -- $ cabal-bundler --openbsd ShellCheck-0.7.2 [ 0.00001] cabal.hackage: Reading Hackage index metadata [ 0.69837] cabal.plan: ... plan input summary TODO ... [ 0.70245] process.0.start: cwd=/tmp/peura-XXXX-c969e8cdbc7903f7 cabal v2-build all --builddir=dist-newstyle --dry-run Resolving dependencies... cabal: Could not resolve dependencies: [__0] trying: fake-package-0 (user goal) [__1] next goal: fake-package:ShellCheck:exe.ShellCheck (dependency of fake-package) [__1] rejecting: fake-package:ShellCheck:exe.ShellCheck-0.7.2 (does not contain executable 'ShellCheck', which is required by fake-package) [__1] rejecting: fake-package:ShellCheck:exe.ShellCheck-0.7.1 (conflict: fake-package => fake-package:ShellCheck:exe.ShellCheck (exe ShellCheck)==0.7.2) [__1] skipping: fake-package:ShellCheck:exe.ShellCheck-0.7.0, fake-package:ShellCheck:exe.ShellCheck-0.6.0, fake-package:ShellCheck:exe.ShellCheck-0.5.0, fake-package:ShellCheck:exe.ShellCheck-0.4.7, fake-package:ShellCheck:exe.ShellCheck-0.4.6, fake-package:ShellCheck:exe.ShellCheck-0.4.5, fake-package:ShellCheck:exe.ShellCheck-0.4.4, fake-package:ShellCheck:exe.ShellCheck-0.4.3, fake-package:ShellCheck:exe.ShellCheck-0.4.2, fake-package:ShellCheck:exe.ShellCheck-0.4.1, fake-package:ShellCheck:exe.ShellCheck-0.3.8, fake-package:ShellCheck:exe.ShellCheck-0.3.7, fake-package:ShellCheck:exe.ShellCheck-0.3.6, fake-package:ShellCheck:exe.ShellCheck-0.3.5, fake-package:ShellCheck:exe.ShellCheck-0.3.4, fake-package:ShellCheck:exe.ShellCheck-0.3.3, fake-package:ShellCheck:exe.ShellCheck-0.3.2, fake-package:ShellCheck:exe.ShellCheck-0.3.1, fake-package:ShellCheck:exe.ShellCheck-0.3.0, fake-package:ShellCheck:exe.ShellCheck-0.4.0 (has the same characteristics that caused the previous version to fail: excluded by constraint '==0.7.2' from 'fake-package') [__1] fail (backjumping, conflict set: fake-package, fake-package:ShellCheck:exe.ShellCheck) After searching the rest of the dependency tree exhaustively, these were the goals I've had most trouble fulfilling: fake-package, fake-package:ShellCheck:exe.ShellCheck [ 6.01458] peu.die: Cannot find an install plan for ShellCheck-0.7.2
