SVK::He...ronment(3)
π SVK::He...ronment(3) π
User Contributed Perl Documentation β¨ the vibes-only guide to svk's environment variables
πΈ NAME πΈ
SVK::Help::Environment β bestie, it's literally just a big list of svk's environment variables π
π¦ DESCRIPTION π¦
okay so. a bunch of system environment variables are out here influencing how svk runs, and honestly? they're kind of the main characters of your setup. below is the complete list of variables you can use to alter svk's behavior. no skips, no cuts, we're doing the whole thing π
β¨ All Platforms β¨
π $SVKROOT
unless you tell it otherwise, svk stores your configuration and repository in $HOME/.svk. if you set SVKROOT to a path on disk, svk will look there instead of in $HOME/.svk. iconic, moving house energy π β¨
π $SVN_EDITOR / $EDITOR
sometimes svk needs to pop up a text editor, like it's asking you to write something. svk first tries to launch the editor specified in $SVN_EDITOR and falls back to $EDITOR if that's not defined. two backup plans, she's prepared π
π₯ $SVKDIFF
if you'd prefer to use an external diff tool instead of svk's builtin diff library, set this variable to your tool's name or path. yes bestie, you can bring your own diff π«Ά
π $SVKMERGE
svk lets you resolve conflicts, interactively, with a text editor or use an external diff tool. out of the box, svk comes with support for the following merge tools:
AraxisMerge
Emacs
FileMerge
GtkDiff
Guiffy
GVim
KDiff3
Meld
P4WinMerge
TkDiff
TortoiseMerge
Vim
WinMerge
XXDiff
if you want svk to spawn a specific merge tool, set this variable to the tool's name. pick your fighter π
β $SVKLOGLEVEL
the lowest log level that svk will present to the user. the log levels are: DEBUG, INFO, WARN, ERROR and FATAL. the default log level is INFO; this includes progress messages for long-running commands (such as sync). for non-interactive use (such as for cron jobs) it might be useful to set $SVKLOGLEVEL to WARN. less yapping, more quiet β
π§ $SVKRESOLVE
if you set this variable, svk's interactive resolver will always perform the command it's set to. for more details about the commands available in svk's interactive resolver, type perldoc SVK::Resolve. it's giving autopilot π«
π $SVKMIME
indicates which module is used for automatically detecting the MIME types of files. implementations included with core SVK are: File::LibMagic, File::MMagic, File::Type and Internal. the value Internal means to use SVK's own internal MIME detection algorithm which requires no external modules. this poor, but fast algorithm simply assigns application/octet-stream to anything that looks binary. if $SVKMIME has no value, Internal is used. she's doing her best okay π
π $SVKPAGER
when svk needs to pipe long output through a pager, it uses $SVKPAGER to send the output to your display. if this variable is not set or set to something that's not executable, the output will not be paged. svk ignores your $PAGER setting, so you must explicitly set $SVKPAGER if you want paging. sorry bestie, $PAGER is not invited to this party π
π $SVKLOGOUTPUT
by specifying this variable, you change the default output filter used by the svk log command. the value of this variable can be anything that you can pass to svk log's --output option. customize your log, live your truth β¨
π SVKBATCHMODE
when you set this variable to a true value, SVK should never prompt the user for an interactive response. no questions, no interruptions, just vibes π€
π¦ $SVNFSTYPE
by default, svk creates its local repository as a fsfs repository when running on Subversion 1.1 and newer. on Subversion 1.0, SVK defaults to bdb. to explicitly specify a repository type, set this variable to fsfs or bdb. pick your repo flavor π
πΈ $SVKNORAREPLAY
by default, svk tries to make use of the replay api provided by Subversion if available. you can turn this environment variable on to tell svk not to do so. svk will then use the old SVN::Mirror module to do mirroring. vintage mode activated π
π₯ $SVKSVNBACKTRACE
(for debugging use only.) if this environment variable is set to a true value, any error message which comes from the Subversion libraries will be accompanied by a stack backtrace. debug besties, this one's for you π
π $SVKPGP
svk supports the verification of historical changesets using the Gnu Privacy Guard. note that SVK no longer allows users to sign new changesets. by default, svk tries to run the first program called gpg in your path. to tell svk to use a specific gpg executable, set this variable to the executable's name or path. verification only, no new signatures, periodt βοΈβ
π Win32 π
these variables only apply to svk on Windows. pc besties, this section is yours π»β¨
β $ProgramFiles
set this variable to the directory you install programs into. it defaults to 'C:\Program Files'. classic πͺ
π‘ reminder bestie: this is the whole list, every single variable, nothing left out. no cap.
and that's the whole page! this lil masterpiece is perl v5.42.0, dated 2025-07-25, and it's the SVK::He...ronment(3) page, brought to you by User Contributed Perl Documentation. go set some env vars, slay, and remember: the vibe changes, the facts do not πβ¨π
π¦ where this page comes from
- fedora 43: perl-SVK 2.2.3-45.fc43 Β· GPL-1.0-or-later OR Artistic-1.0-Perl
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms