Esta es la versión actual. · Fecha de publicación:
Archivos de instalación v0.4.7
| Arquitectura | Tipo | Ámbito | Tamaño del archivo | Descargar | SHA256 |
|---|---|---|---|---|---|
| 64 bits | EXE (NSIS) | Usuario actual | — | github.com | VirusTotal |
El enlace y el SHA256 proceden del manifiesto comunitario del Administrador de paquetes de Windows. Conviene comparar el hash del archivo descargado antes de ejecutarlo.
Notas de la versión
Viff 0.4.7 fixes svn discovery when launching from Finder on macOS with Homebrew and makes the Subversion executable setting always accessible in General settings.
Highlights
This patch release focuses on Subversion setup, fixing automatic svn lookup on macOS and allowing a custom svn path to be configured before opening a working copy.
🛠 Fixes
- When no explicit svn path is configured and svn is not on PATH on macOS, Viff now falls back to the standard Homebrew prefixes (/opt/homebrew/bin/svn and /usr/local/bin/svn) while keeping explicit configuration highest priority.
- Settings → General → Subversion executable is now always shown so a custom svn path can be configured before opening a Subversion working copy, and saving applies it immediately to the SVN backend.
Upgrade instructions
- Upgrading from v0.4.6: replace or install over the previous version; no manual settings migration is needed.
- macOS: choose the Apple Silicon or Intel DMG, quit the old version, open the DMG, and replace Viff.app in Applications.
- Windows: quit the old version and run the x64 installer.
- Windows portable: extract the archive, enter its directory, and run viff.exe without installing.
- Debian/Ubuntu: run sudo apt install ./viff-v0.4.7-linux-amd64.deb.
- Linux portable: extract the archive, enter its directory, and run ./viff after installing the required system libraries.
- Install Git separately on PATH, and check the release guide for Linux dependencies.
Compatibility and known issues
- Subversion support requires a locally installed svn; when left blank, Viff checks PATH first and then the standard Homebrew prefixes on macOS, and nonstandard locations can be set in General settings.
- macOS requires version 13 or later; Linux needs a working graphical session, rendering backend, and the system libraries listed in the release guide.
- The macOS app is ad-hoc signed without Developer ID signing or notarization; the Windows installer is not Authenticode signed, so the system may show a security prompt; remote repositories remain read-only observation.
- Install only files from the project release page after checking their checksums; verify the source if the operating system blocks them.