*> Would anyone who uses a Mac and is reasonably Homebrew-literate like to pick this up?*
My contributions to Homebrew are minimal at best, but I'll see what I can do. Having a man-db formula will quicken development/testing of Roff.js <https://github.com/Alhadis/Roff.js>, because switching between man(1) flavours will be as easy as running `brew (un)link man-db`. =) FYI, there's also a Linux port <http://linuxbrew.sh/> of Homebrew, though I've never tried it. On Mon, 28 Jan 2019 at 09:26, Colin Watson <cjwat...@debian.org> wrote: > On Thu, Jan 24, 2019 at 04:21:51PM +0000, Colin Watson wrote: > > On Fri, Jan 25, 2019 at 02:10:32AM +1100, John Gardner wrote: > > > There was an attempt to get man-db > > > <https://github.com/Homebrew/homebrew-core/pull/25376> accepted in > > > Homebrew, but a patch was needed for macOS support, which Homebrew > required > > > upstream to accept before they'd support it. > > > > FWIW, this was gnulib upstream, not man-db / libpipeline upstream (i.e. > > me). > > > > If somebody could point me to where I could get SSH access to a macOS > > box with the right set of build tools installed, I'd be happy to try to > > get it working properly. > > We got this sorted out so that libpipeline and man-db build without > patches in Homebrew: > > https://github.com/ylluminarious/homebrew-man-db/issues/1 > > However, the original submitter is reluctant to submit these formulae to > the Homebrew maintainers again due to their earlier conflict (see the > end of that issue). I'm not a good person to do it since I don't use a > Mac. Would anyone who uses a Mac and is reasonably Homebrew-literate > like to pick this up? I don't think the conflict should recur since the > upstream build is clean now, and I'd be happy to do whatever other > upstream support is needed. > > Thanks, > > -- > Colin Watson [cjwat...@debian.org] > >
