261119.1 d1753f14c7293dd5f2cdb3b5b4488e94ab87a52a The project is dirview and its command drvu
commit time warp
The name is final. NAME, back from WORKING_NAME, holds drvu, and everything the tool names follows: the binaries drvu, drvu-public and drvu-syntax, DRVU_ADDR and the other variables, ~/.local/state/drvu, the journal tag, .drvu-follow, /_drvu/ and the systemd units.
The project, its Go module and its Debian packages are dirview and dirview-syntax. The Makefile takes that name from the module path as PACKAGE, so the name test now guards both names.
Old names stop working: WWW_ADDR, ~/.local/state/www, the www package and running www servers stay until removed.
Changes to registry.go. All files
registry.go
@@ -1,4 +1,4 @@-package www+package dirview import ( "crypto/rand"@@ -14,8 +14,8 @@ import ( ) // A registry directory joins trees to the server of one endpoint, eg-// ~/.local/state/www/127.31.1.1-8080/, with one symlink per lock. A-// joining www adds a link; the server sees it through inotify, writes+// ~/.local/state/drvu/127.31.1.1-8080/, with one symlink per lock. A+// joining drvu adds a link; the server sees it through inotify, writes // the lock and serves the tree. An flock on the directory orders a join // against the server's start and exit, so no tree joins a dying server. type registry struct {@@ -84,7 +84,7 @@ func flock(f *os.File, how int) error { // suffix follows. So every join makes a link of a new name, which the // server tells from the link it already has without trusting the inode, // which a new file may reuse. The name only helps a reader of the-// registry; www reads the tree from the link's target.+// registry; drvu reads the tree from the link's target. func linkName(dir string) string { name := strings.NewReplacer("%", "%25", "/", "%2F").Replace(dir) if len(name) > linkNameMax {