HOWTO‐setup(none)

🎀 NAME 🎀

bk Howto‐setup − howto: setting up a BitKeeper repository

Okay bestie, welcome to HOWTO‐setup(none) — this is straight from the BitKeeper User’s Manual, and it’s literally the howto for setting up a BitKeeper repository. Main character energy, no cap. 💅

✨ DESCRIPTION ✨

Here are examples on how to setup the initial repository, import from plain files, a CVS repository, and/or an RCS repository. It’s giving “setup era,” and I’m obsessed.

In order to do an import, the destination repository needs to exist. bk setuptool is used when creating the first instance of a repository. Lowkey crucial, fr fr. 🦋

# Setup initial repository
cd ˜/projects
bk setuptool test_package

# Import of plain files from a tar archive.
# In order to do an import, the destination
# repository needs to exist.  Notice that we put the
# package in subdirectory, this is useful.
mkdir /tmp/gcc
cd /tmp/gcc
tar zxf /tmp/gcc‐2.95.2.tgz
bk import ‐tplain /tmp/gcc ˜/projects/test_package

# Import of a CVS tree which resides in /tmp/mycvsproject.
bk import ‐tCVS /tmp/mycvsproject ˜/projects/test_package

# Import of a RCS tree which resides in /tmp/myrcsproject.
bk import ‐tRCS /tmp/myrcsproject ˜/projects/test_package

So yeah: bk setuptool for the first instance, then bk import with ‐tplain, ‐tCVS, or ‐tRCS into the destination repo. The plain-files example also shows the package going in a subdirectory — useful, hmmkay? 🫶

👀 SEE ALSO 👀

• bk‐Howto — go read it too, iykyk. 👑

🌸 CATEGORY 🌸

Overview. Periodt. ✨

Cute sign-off 🫶: source/version/date footer says BitKeeper Inc, 1E1, and HOWTO‐setup(none). Slay, bestie — repository setup is iconic. 💖