Link Rule

Rule

• If there is $home, replace it with $scoopdir\persist\abgox.abyss.
• Otherwise, replace the drive letter with $scoopdir\persist\abgox.abyss.

TIP

Why not follow Scoop's per-app directory convention?

• Scoop's persist convention gives each application its own directory (persist\<app>), and it rests on two premises:
  1. Data lives inside the install directory.
  2. Data belongs to that one application.
• However, link targets standard data paths.
  1. They should have been stored in Windows' standard data directories.
     • They are centralized with no data isolation.
     • The persist convention results in inconsistent data structures, which conflicts with link by design.
  2. Data in standard data directories theoretically belongs to a single application only.
     • A centralized architecture inherently allows multiple applications to read and write the same data.
     • Cross-application read and write access is determined by the applications themselves, not enforced by Scoop via data isolation restrictions.

Example

• Microsoft.VisualStudioCode stores its data in $env:AppData\Code and $home\.vscode
  • $home\AppData\Roaming\Code => $scoopdir\persist\abgox.abyss\AppData\Roaming\Code
  • $home\.vscode => $scoopdir\persist\abgox.abyss\.vscode

---

• It directly uses the following way to define the link in abyss:

  "link": [
      "$env:AppData\\Code",
      "$home\\.vscode"
  ],

• abyss only needs you to specify the data directories, and it does not need to specify the target directory.
• This ensures the uniformity of data persistence, and also lowers the risk of errors and cognitive load in manually defining directory structures.