REDO-STAMP(1)

πŸ“¦
version 4.0.7 Β· 2 versions
, in arch rolling, nixos 26.05, nixpkgs unstable

πŸ¦‹ REDO-STAMP(1) πŸ¦‹

okay bestie, welcome to the General Commands Manual page for redo-stamp β€” it’s giving build-tool bestie energy, and the whole point is: feed it data on standard input and it stamps that data as a dependency of the current redo(1) target. πŸŽ€

πŸ’– NAME πŸ’–

redo-stamp β€” rebuild target files depending on data given on standard input. literally the whole name-and-one-liner, periodt. ✨

🌸 SYNOPSIS 🌸

[command] | redo-stamp

✨ DESCRIPTION ✨

okay so redo(1) is the tool for building files and rebuilding them whenever any of their dependencies changed. πŸ‘‘

redo-stamp, when it’s invoked from a dofile, adds a dependency of the current redo(1) target on the data given on standard input. so yes: stdin data becomes build-dependency material, no cap. πŸ’…

If the data given on standard input to redo-stamp has not changed since the last build, the current redo(1) target is not rebuilt and is marked as up to date. cute, efficient, slay. πŸ¦‹

And if you need to make sure redo-stamp actually checks the current target’s validity? You can use redo-always(1) to mark the current target as always out of date. that’s the move. πŸ”₯

πŸŽ€ EXAMPLES πŸŽ€

consider these two files, all.do and b.do β€” build-script besties:

all.do

#!/bin/sh
redo-ifchange b

b.do

#!/bin/sh
redo-always
echo 'input a line of text:' >&2
line | redo-stamp
date +%s

Invoking redo(1) in a directory with these files will build a file named b containing a timestamp. ⏰

The next time redo(1) is invoked, it will only rebuild b if the output of line(1) changed since the last build. You can verify that by invoking redo(1) repeatedly and examining the timestamp b after each invocation, then changing the input to line(1), invoking redo(1) again, and examining the timestamp again. see? main character build behavior. πŸ’«

🧚 HISTORY 🧚

redo-stamp was designed by Avery Pennarun and implemented by Γ†lla Chiana Moskopp. iconic collaboration, honestly. 🫢

πŸ‘‘ AUTHOR πŸ‘‘

redo-stamp and this man page were written by Γ†lla Chiana Moskopp. periodt. πŸ’œ

Copyright Β© 2014-2017 Γ†lla Chiana Moskopp. License AGPLv3+: GNU Affero GPL version 3 or later <http://www.gnu.org/licenses/agpl-3.0.html>. This is free software: you are free to create and redistribute it. There is NO WARRANTY, to the extent permitted by law. ⚠️

⭐ SEE ALSO ⭐

πŸ’€ BUGS πŸ’€

None so far. genuinely none on the board, bestie. πŸŽ€


sign-off, bestie: that was REDO-STAMP(1) from the General Commands Manual πŸ¦‹ the page doesn’t list a separate version or date, so no cap, we’re not inventing one β€” bye! πŸ’…βœ¨

πŸ“¦ where this page comes from