public inbox for goredo-devel@lists.cypherpunks.ru
Atom feed

From: goredo <spacefrogg-goredo@spacefrogg•net>
To: goredo-devel@lists.cypherpunks.ru
Subject: [PATCH] Don't create nested target directories automatically
Date: Fri, 15 Apr 2022 06:10:58 +0000 (UTC)	[thread overview]
Message-ID: <e3c9106d-4eb8-4666-b645-821880a12284@spacefrogg.net> (raw)
In-Reply-To: <20220415005559.3682838-1-ac@acha.ninja>

It was a concious decision that redo creates target directories. Now, every default*.do file must be aware of file hierarchies, which is quite annoying.

It also doesn't solve your problem, because, now, your default.do file also contains a line like:
`mkdir -p $(dirname $2)`.

This means, the garbage directory is also created for your mistyped target unless you take special precautions in all of your default.do files to limit their scope of directories they are concerned with. (before you call mkdir) You cannot and you don't always want to do this. E.g. in a very general default.o.do to compile a C file.

The general contract with redo is, that the position of the .do file in the directory hierarchy limits its scope.

Regards,
–Michael

next prev parent reply	other threads:[~2022-04-15  6:11 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-15  0:55 [PATCH] Don't create nested target directories automatically Andrew Chambers
2022-04-15  6:10 ` goredo [this message]
2022-04-15  6:49   ` Andrew Chambers
2022-04-15  7:15     ` goredo
2022-04-15  7:31       ` Andrew Chambers
2022-04-15  9:28         ` goredo
2022-04-15 12:00           ` Andrew Chambers
2022-04-15 13:17             ` goredo
2022-04-15 13:39               ` Andrew Chambers
2022-04-15 13:58                 ` goredo
2022-04-15 16:23               ` Sergey Matveev
2022-04-16  0:36                 ` Andrew Chambers
2022-04-15 16:23     ` Sergey Matveev
2022-04-15  6:57   ` Andrew Chambers
2022-04-15 16:23 ` Sergey Matveev