On Tue, May 10, 2022, 08:32 Richard Eckart de Castilho <r...@apache.org> wrote:
> On 10. May 2022, at 17:02, Randall Leeds <rand...@apache.org> wrote: > > > > You don't need git. That's the source of my surprise at your error. You > > also don't need make, you can just run "yarn lint" and "yarn test". The > > makefile is there as a convenience for the muscle memory of "make check", > > "make dist", and "make distcheck". > > I don't have yarn installed as a system-wide tool ;) > > Would this also work? > > % npm i > % npm run lint > % npm run test > > ... or would this miss anything substantial? > > "npm run lint" doesn't seem to produce much output, but "npm run test" > produces a nice test report. > Yarn is required. Maybe there is enough compatibility in the workspaces implementations that npm works now, but I've not tested it. Looking back at your original message, does "make check" actually fail, or not? I'm seeing the "fatal: ..." but I think that's actually non-fatal messaging that should be silent in the Makefile, wherein the Makefile tries to figure out whether this build is on a release branch of git, to use that information in "make dist". Any targets that don't depend on "dist" shouldn't actually fail. That may just be overly verbose output. >
