BK-SETUPTOOL(1)
πΈ bk setuptool β the BitKeeper User's Manual, but make it cute πΈ
okay so bestie, welcome to bk setuptool β it's literally a graphical front-end to the BitKeeper setup command, and it's about to hold your hand through making a whole repo. we're in the BitKeeper User's Manual today, so buckle up π
β¨ SYNOPSIS β¨
bk setuptool [directory]
that's it. that's the whole vibe check. one optional directory, no cap π
π¦ DESCRIPTION π¦
so bk setuptool is a graphical interface for creating new BitKeeper repositories. yes, graphical, like, with windows and forms and everything. a glow-up from typing stuff into a terminal, honestly π«Ά
the whole point of the tool is to help you enter all the information you need to create a repository, by stepping you through a series of input forms and prompts. it's giving guided tour. it's giving main character energy. it walks you through, one step at a time β¨
you'll be prompted for additional information that gets stored in the config file for the repository. and heads up β different types of repositories will require slightly different sets of data, so don't be surprised if the questions change depending on what you're building π
after all the information has been entered, you get a chance to review everything that's going to be put into the config file before the repository is created. love that for you. a little preview moment, a little "wait, let me check that" β iconic π
and then: when the repository is created, the config file is stored as a normal revision controlled file, so you can totally go back and edit the file at a later date. no big deal. it's reversible. we love a reversible situation π
now for the big tip β if you're going to be creating several repositories that use the same configuration information (like, say, contact information, the classic), you may create a system-wide default config file at /etc/BitKeeper/etc/config.template. this has the same format as a regular config file. bk setuptool will look for this file and, if found, use the data in the file to set the default values when creating a new repository. so you fill it in once and it's lowkey doing your homework forever π§
π₯ EXAMPLES π₯
okay let's say you want to create a repository named /projects/helloworld. you literally type this:
bk setuptool /projects/helloworld
and then it will prompt you for information to place in the config file, and then create a project hierarchy rooted at /projects/helloworld. the config file with all the data you entered ends up at:
/projects/helloworld/BitKeeper/etc/config
slay. a whole repo, just like that π
and ngl, you do not need to include the name of a directory on the command line. if you don't include it, you'll be required to enter a name during one of the configuration steps. so like, either way works β the tool's got you π«Ά
π BINDINGS π
- ENTER β perform the default action, which is either to go to the next step, or create the repository if you're on the final step. one button, two jobs, we stan an efficient queen β¨
- TAB β moves between input fields. hop, hop, hop π¦
you may also use your system's cut, copy and paste keys in the input fields. yes, all of them. go wild π
π SEE ALSO π
bk-config-etcbk-setup
go read those next, iykyk π
β CATEGORY β
GUI-toolsRepository
and that's the page, bestie!! π this whole thing was brought to you by BitKeeper Inc β source/version tag 1E1, manual section none, dated as bk setuptool(none) in the footer of the original. no cap, that's the sign-off πβ¨π¦
π¦ where this page comes from
- alpine 3.24: bitkeeper-doc 7.3.3-r1 Β· Apache-2.0
- Copyright (c) 1998-2015 BitKeeper Inc
- Copyright (C) 1989, 1990, 1991, 1992, 2001, 2002, 2003, 2004, 2005 Free Software Foundation, Inc
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms