public inbox for goredo-devel@lists.stargrave.org
Atom feed

From: "Christian G. Warden" <cwarden@xerus•org>
To: goredo-devel@lists.cypherpunks.su
Subject: redo-stamp
Date: Mon, 31 Mar 2025 12:58:20 -0500	[thread overview]
Message-ID: <Z+rXvAidoqlz4p5L@xerus.org> (raw)

I'm exploring switching from apenwarr's redo to goredo, and found
that one of my common conventions doesn't work.

I frequently use redo for data pipelines.  This typically involves
retrieving some data from a remote resource.  Fetching lots of data
can be time consuming.  Working with data that's an hour or a day old
if often fine.

So the convention I follow in data.csv.do looks like this:
redo-ifchange date
... fetch data > $3

And date.do looks like this:
redo-always
date +%Y%m%d | redo-stamp

When I run `redo data.csv`, data is only fetched if I haven't already
fetched data today.

If I'm doing the same analysis with data from multiple remote sources,
I'll similarly have data.csv.do include `redo-ifchange user`, where
user.do looks like:
redo-always
force active | redo-stamp

So if I change my active user, data.csv will be out of date.

I can of course generate `date` and `user` files rather than use
redo-stamp, but is there any reason to intentionally not support this
functionality?  Any other suggestions?

Thanks,
Christian

next             reply	other threads:[~2025-03-31 18:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-31 17:58 Christian G. Warden [this message]
2025-04-02  7:45 ` redo-stamp Sergey Matveev
2025-04-02 10:54   ` redo-stamp spacefrogg
2025-04-03 22:45     ` redo-stamp Andrew Chambers
  -- strict thread matches above, loose matches on Subject: below --
2021-10-27 17:18 Multiple calls to redo-* for same target results in multiple .rec entries goredo
2021-10-31  8:21 ` Sergey Matveev
2021-11-04 15:35   ` goredo
2021-11-09  9:13     ` Sergey Matveev
2021-11-09 13:43       ` goredo
2021-11-10 12:22         ` redo-stamp Sergey Matveev