Opened at 2008-06-01T20:13:27Z
Closed at 2008-06-03T01:01:52Z
#431 closed defect (fixed)
CLI: The relationship between aliases and root_dir.cap is confusing.
| Reported by: | nejucomo | Owned by: | warner |
|---|---|---|---|
| Priority: | major | Milestone: | 1.1.0 |
| Component: | documentation | Version: | 1.0.0 |
| Keywords: | usability cli | Cc: | |
| Launchpad Bug: |
Description (last modified by warner)
What is it? Don't aliases supercede root_dir.cap? Why is root_dir.cap still mentioned in the --help output and docs/using.html?
Which commands use root_dir.cap, and which use aliases?
Change History (2)
comment:1 Changed at 2008-06-01T21:43:25Z by warner
- Component changed from unknown to documentation
- Description modified (diff)
- Milestone changed from eventually to 1.1.0
- Owner changed from nobody to warner
- Status changed from new to assigned
comment:2 Changed at 2008-06-03T01:01:52Z by warner
- Resolution set to fixed
- Status changed from assigned to closed
I think this is better now, with the docs fixes in 3e8d58767fa370a4 and 313876263d698b53. I'm going to close this.. if those docs don't seem clear, feel free to re-open it.
Note: See
TracTickets for help on using
tickets.
root_dir.cap is used to provide the target of the default "tahoe:" alias, for compatibility with existing nodes (so "tahoe ls" does the same thing for 1.0 and 1.1).
Yeah, docs need to be cleaned up to capture this. Moving to 1.1.0 milestone, it's probably important enough to pull in.