Re: [dev] cat -v

2022-01-31 Thread Kyryl Melekhin
Greg Minshall  wrote:

> i think it was a Rob Pike paper, maybe Usenix, probably in the 1990s.
> the idea, iirc, is that you can always pipe the output of cat(1) into
> od(1), or into any other program you wanted, so keep cat simple.  good
> paper (but, sometimes i do `cat -v`).

By the way, here is excerpt from POSIX manual:

RATIONALE
Historical versions of the cat utility include the -e, -t, and -v,
options which permit the ends of lines,  characters, and invisible
characters, respectively, to be rendered visible in the output. The
standard developers omitted these options because they provide too fine
a degree of control over what is made visible, and similar output can
be obtained using a command such as:


sed -n l pathname

The latter also has the advantage that its output is unambiguous,
whereas the output of historical cat -etv is not.



Re: [dev] requirements of build systems

2022-01-31 Thread Страхиња Радић
On 22/01/31 12:10, Petros Pateros wrote:
> What would you expect from a build system? Should it trust mtime?
> Is it responsible for verifing the file's contents for actual changes?
> More generally, what are the key features that make a build system useful?

apenwarr/redo is the implementation of djb redo I settled on for my programs. It
has the most features among the current implementations. For redistribution, it
has a shell script named "do", so even if users don't have full apenwarr/redo
installed on their system, they can execute

$ ./do -c

to build my programs, or

# ./do -c install

to install them.


signature.asc
Description: PGP signature