From: Patrick Mahoney <pat@polycrystal.org>
To: supervision@list.skarnet.org
Subject: "redo" behavior in subdirectory
Date: Fri, 25 Jan 2019 13:49:34 -0600 [thread overview]
Message-ID: <20190125194934.g456z24hi6sujzdl@Patricks-MacBook-Pro.local> (raw)
I'm comparing two implementations of "redo":
First, jdebp/redo 1.4 [1]
Second, apenwarr/redo 0.41 [2]
[1] http://jdebp.eu/Softwares/redo/
[2] https://github.com/apenwarr/redo
Given a project "toplevel" with a subdirectory "subdir" where one's current dir is "toplevel":
In jdebp implementation, running "redo subdir/target" invokes target.do with working dir "toplevel"
In jdebp implementation, running "cd subdir && redo target" creates a new .redo database in subdir
In apenwarr implementation, running "redo subdir/target" invokes target.do with working dir "toplevel/subdir"
In apenwarr implementation, running "cd subdir && redo target" reuses "toplevel/.redo" (assuming it already exists)
The apenwarr implementation seems more useful for constructing a build system
for a project with many nested subprojects, but I may be missing something (I
don't have much experience with any redo implementation). Anyone have comments
on this, or example nested subprojects using "redo"?
--
Patrick
reply other threads:[~2019-01-25 19:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190125194934.g456z24hi6sujzdl@Patricks-MacBook-Pro.local \
--to=pat@polycrystal.org \
--cc=supervision@list.skarnet.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).