tahoe-lafs/trac-2024-07-25

mkdir-immutable probably shouldn't implicitly create (mutable) intermediate directories #920

New issue

Open

opened 2010-01-20 07:04:19 +00:00 by davidsarah · 0 comments

davidsarah commented

2010-01-20 07:04:19 +00:00

Owner

From #903:

... I don't think that automatically creating the intermediate directories makes a lot of sense for the mkdir-immutable-with-path operations:

if the intermediate directories are created as immutable, then they will only ever have one child, and that isn't very useful.

if they are created as mutable, that's irregular and might not be what the user (or programmer, if they're not paying close attention to docs) expected.

So I think that a mkdir-immutable-with-path should fail if the intermediate directories don't already exist (in which case, they must obviously be mutable). Explicit Is Better Than Implicit.

The current code creates the intermediate directories as mutable.

From #903: > ... I don't think that automatically creating the intermediate directories makes a lot of sense for the `mkdir-immutable`-with-path operations: > * if the intermediate directories are created as immutable, then they will only ever have one child, and that isn't very useful. > * if they are created as mutable, that's irregular and might not be what the user (or programmer, if they're not paying close attention to docs) expected. > So I think that a `mkdir-immutable`-with-path should fail if the intermediate directories don't already exist (in which case, they must obviously be mutable). Explicit Is Better Than Implicit. The current code creates the intermediate directories as mutable.

tahoe-lafs added the

code-frontend-web

labels 2010-01-20 07:04:19 +00:00

tahoe-lafs added this to the undecided milestone 2010-01-20 07:04:19 +00:00

tahoe-lafs modified the milestone from undecided to 1.7.0

2010-02-27 06:40:56 +00:00

tahoe-lafs modified the milestone from 1.7.0 to eventually

2010-06-17 04:37:16 +00:00

Sign in to join this conversation.

No labels

LeastAuthority.com automation

cannot reproduce

code-frontend-cli

code-frontend-ftp-sftp

code-frontend-magic-folder

code-frontend-web

code-peerselection

dev-infrastructure

somebody else's problem

was already fixed

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: tahoe-lafs/trac-2024-07-25#920

No description provided.