App::K...nt::CVS(3pm)
β¨ NAME β¨
App::KGB::Client::CVS β bestie, it's the KGB interface to CVS π
πΈ SYNOPSIS πΈ
use App::KGB::Client::CVS;
my $client = App::KGB::Client::CVS(
# common App::KGB::Client parameters
repo_id => 'my-repo',
...
# CVS-specific
cvs_root => $ENV{CVSROOT},
author => $ENV{USER},
directory => 'module/dir',
);
$client->run;
π¦ DESCRIPTION π¦
okay so App::KGB::Client::CVS is literally the CVS-specific girly π
β it handles the whole "get me the commits and the changes" thing for App::KGB::Client. That's its job. That's the whole vibe. no cap.
π CONSTRUCTOR π
new ( { initializers } )
Standard constructor, iconic, never misses. It accepts an inline hash with the initial field values you wanna set. periodt. β¨
π FIELDS π
App::KGB::Client::CVS defines these extra fields on top of the usual ones:
cvs_root(mandatory) β the physical path to the CVS root directory. like, an actual path on disk, bestie, not a vibe. π«Άauthorβ the user name of the commit author.directoryβ the path to the directory this change is in, relative to the CVS root.
And the convention here? By convention, the first path member gets taken as a module. iykyk π
π METHODS π
describe_commitβ the very first time you call this method, it parses STDIN, figures out what's in the commit, and hands you back an instance of theApp::KGB::Commitclass describing that commit. π
Every invocation after that first one? Returns undef. Like, it already did the thing, she's done, she's resting. π
ngl bestie, remember:cvs_rootis mandatory and the first path member ofdirectorybecomes the module. That's just how she works. π
perl v5.40.1 πΈ 2026-07-10 β that's the version and date, mwah, thanks for reading my page, ily, go slay some commits πβ¨π
π¦ where this page comes from
- ubuntu stonking: kgb-client 1.62-4 Β· GPL-2.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms