k3b-handoff

name	k3b-handoff
description	Use when growisofs misbehaves on a particular drive/media combo and the user wants to fall back to k3b's GUI to burn one batch manually.

K3b Handoff

Manual fallback. Stage one batch's files (or symlinks) into a temp folder and launch k3b --datacd <path> so the user can drive the burn through the GUI.

When to use

• growisofs repeatedly fails on a specific drive/media combination.
• The user prefers to use k3b for a particular batch (e.g. multisession, custom session settings).

Inputs to gather

• Disc number (which planned batch to stage).
• Stage mode — symlink (default, fast, no extra disk use) or copy (slower, but safe across removable media).

Procedure

1. Verify k3b is installed (command -v k3b). If not, instruct sudo apt install k3b and abort.
2. Create staging dir: $WORKSPACE/k3b-staging/disc-NN/.
3. Read $WORKSPACE/batches/disc-NN/filelist-graftpoints.txt. For each archive_path=source_path:
   • symlink mode: ln -s <source_path> <staging>/<archive_path> (mkdir -p parents as needed).
   • copy mode: cp --reflink=auto <source_path> <staging>/<archive_path>.
4. Print total staged size and time estimate (copy mode only).
5. Launch: k3b --datacd "$WORKSPACE/k3b-staging/disc-NN/" &. Print the PID.
6. Tell the user: confirm the project in k3b, set burn speed manually, click Burn. Plugin does not automate further once k3b owns the session.
7. Offer to clean up the staging dir after the user reports the burn done.

Output / side effects

• $WORKSPACE/k3b-staging/disc-NN/ populated.
• k3b launched with the project preloaded.

Safety / constraints

• Symlink mode means the source must remain mounted/available during the k3b burn.
• Do not delete the staging dir automatically — wait for explicit user confirmation.