rancid-cvs(1)

💖 rancid-cvs — the manual page, but make it cute 💖

okay bestie, this is rancid-cvs(1) from the General Commands Manual section, and honestly? she's the setup queen. she gets your whole rancid world born. let's get into it 🫶

✨ NAME ✨

rancid-cvs — initialize CVS, Subversion or git and rancid group files and directories 💅

🌸 SYNOPSIS 🌸

rancid-cvs [-V] [-f config_file] [group [group ...]]

🦋 DESCRIPTION 🦋

So. rancid-cvs creates the directories and router.db(5) for each rancid group, and it handles the whole revision control system situation — that's CVS, Subversion or git — in the location defined by the CVSROOT in rancid.conf(5). no cap, that's the job. 💖

⚠️ she must be run after the initial installation, and again whenever a rancid group is added. like, this is not optional, bestie.

Also important: if CVSROOT is a URL, rancid-cvs will not initialize the repository — the user has to do that themselves. it's giving "you're on your own for that part" 😭

Here's how the whole thing flows, fr fr:

rancid-cvs reads rancid.conf(5) to configure itself, then proceeds with the initialization. First the CVS, Subversion or git repository, if necessary — and then for each of the rancid groups, either those listed on the command line or those in the variable LIST_OF_GROUPS from rancid.conf(5) if the argument is omitted. main character energy, she handles both paths ✨

And here's the slay part: running rancid-cvs for groups which already exist will not cause problems. 👑

• if the group's directory already exists → the import into the revision control system is skipped 🙈
• if its router.db(5) already exists → it will not be altered 🎀

idempotent queen, we love to see it.

The command-line options are as follows:

🎀 OPTIONS 🎀

• -V — prints package name and version strings. that's it, that's the vibe ✨
• -f group_config_file — specify an alternative rancid.conf. heads up though: the global rancid.conf file is read by rancid-run. 🫶

okay and now for the actual life advice section:

The best method for adding groups is by adding the group name to LIST_OF_GROUPS in rancid.conf(5), then run rancid-cvs.

💀 Do not create the directories manually. allow rancid-cvs to do it. she's got it, let her cook 🔥

🌈 SEE ALSO 🌈

cvs(1), git(1), rancid.conf(5), router.db(5), svn(1)

💀 CAVEATS 💀

okay this one's the plot twist, so listen up:

In the case of git, the groups are not exactly imported into the repository — rather, a new repository is created for it, due to the way that git handles, what it calls, sparse checkouts. 😭

Instead, each group is a separate repository under the CVSROOT directory. so like, they're all roommates in the CVSROOT house but each one has her own room 🏠✨ iykyk

and that's the whole page, bestie!! no notes. this was written way back on 18 December 2014, and it's still out here living its rancid-cvs(1) truth. periodt 💅🦋🌸