Make --basedir a global option. #706
Labels
No Label
0.2.0
0.3.0
0.4.0
0.5.0
0.5.1
0.6.0
0.6.1
0.7.0
0.8.0
0.9.0
1.0.0
1.1.0
1.10.0
1.10.1
1.10.2
1.10a2
1.11.0
1.12.0
1.12.1
1.13.0
1.14.0
1.15.0
1.15.1
1.2.0
1.3.0
1.4.1
1.5.0
1.6.0
1.6.1
1.7.0
1.7.1
1.7β
1.8.0
1.8.1
1.8.2
1.8.3
1.8β
1.9.0
1.9.0-s3branch
1.9.0a1
1.9.0a2
1.9.0b1
1.9.1
1.9.2
1.9.2a1
LeastAuthority.com automation
blocker
cannot reproduce
cloud-branch
code
code-dirnodes
code-encoding
code-frontend
code-frontend-cli
code-frontend-ftp-sftp
code-frontend-magic-folder
code-frontend-web
code-mutable
code-network
code-nodeadmin
code-peerselection
code-storage
contrib
critical
defect
dev-infrastructure
documentation
duplicate
enhancement
fixed
invalid
major
minor
n/a
normal
operational
packaging
somebody else's problem
supercritical
task
trivial
unknown
was already fixed
website
wontfix
worksforme
No Milestone
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Reference: tahoe-lafs/trac-2024-07-25#706
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Most commands operate on a specific node basedir, so making --basedir a global option would add consistency.
As it is, some commands, such as create-alias do not support a basedir other than the default.
If users want the cli to be strict/pedantic, subcommands which do not rely on --basedir might issue a warning when it is set. Otherwise ignoring it seems safe.
(Update: we actually changed
-d
/--node-directory
to be the global option.)yeah, good idea
#715 has a patch for this ticket. The unified option is spelled
-d
or--node-directory
.In [4614/ticket798]:
Applied to trunk in changeset:f952532f0822fbe7 changeset:54a9ba8232e2b8e9 changeset:a7c474a09893b9aa. NEWS changes were in changeset:0ae556c00ac79d4f changeset:2b15f35b867cebbd.