phoebos

It was self-assessed:

> When we say ‘vigorous’ we mean activities that make you sweat, increase your heart rate or increase your breathing. Please think about vigorous activities that you may have done at home or at places of work other than your home, as well as vigorous recreational activities or conditioning exercises. Please think over the last year and indicate how often you participate in vigorous activities.

It's small compared to the size of the card, sure, but not small for typical modern lithography techniques.

As you noted, I said that the problems stems from sudo not setting PWD, hence `sudo make` doesn't inherit PWD. I'm not calling that a bug in sudo, but it was a bug in the specific makefile which assumed PWD to be set always.

A good solution to the problem is for make to set the PWD macro. BSD make already does this.

> It can get if from the environment like every application does

Well no, applications either read an environment variable or use getcwd(2).

I mostly agree (I was working with sudo make install in order to package neatroff). However, most of the build scripts which generate binary packages for distros etc use `make install`, usually with DESTDIR set, so it's not irrelevant.

I also think `sudo make install` should at least work as expected in this one case, especially because this project isn't widely packaged so most users will be building from source.

I would say it is a make bug in that POSIX make has no good way to get PWD. Not necessarily a bug even, but an annoyance.

Yes, the official Lua implementation is written in a very widely supported subset of C, so is probably one of the most portable languages along with C. Lua might well be a bit more concise for a task like this string processing, but in such as case it's just syntactic sugar really. The C is uncomplicated and efficient.

The separate tools you're probably thinking of are `pkgconf` and `pkg-config`.

Everyone and their dog can compile C, and the initial purpose of this project was to get something working on Windows. As you say, this is a relatively uncomplicated program, and there's certainly no need for higher-level features.

Is the only time you choose C when you need manual memory management? I suspect that had nothing to do with their decision.