|
NAMEbk here - list or change the set of populated repositories
SYNOPSISbk here [set|check] [-@URL] [-fq]
[alias | comp]
SETTING THE SET OF POPULATED COMPONENTS AND/OR ALIASESbk here set [-@URL] [-fq] alias | component ... LISTING POPULATED ALIASESbk here [-v] POPULATING COMPONENTS AND/OR ALIASESbk populate [-@URL] [-fq] alias | component ... CHECKING COMPONENT AVAILABILITYbk here check [-@URL] [-qv] [alias | component] ... UNPOPULATING COMPONENTS AND/OR ALIASESbk unpopulate [-@URL] [-fq] alias | component ... SETTING THE SET OF POPULATED COMPONENTS AND/OR ALIASESbk here set [-@URL] [-fq] alias | component ... DESCRIPTIONThe bk here, bk populate, and bk unpopulate commands are used to manage the set of populated aliases and/or components in a nested collection. The initial set of populated aliases are determined when a nested collection is cloned. If no aliases are specified on the clone command line then the set is specified via the clone_default configuration variable (which is "ALL" if not found). If one or more aliases are specified, then only the repositories implied by those aliases are populated. The bk here command can be used to list what is here, set what is here, or check what is here and list other places where components can be found. The -a option to bk here check prints out all URLs in which the component(s) can be found. If no alias parameters are listed with bk here check, then only the missing components are checked. The bk populate command can be used to add to what is here. The bk unpopulate command can be used to remove from what is here. In order to preserve any local work, before removing any components bk here needs to be able to verify everything being removed exists elsewhere. The bk superset command will be run, which searches for local changesets, deltas, modifications, extra files, etc. See -f below for how to skip this check. Note that it is not (currently) possible to remove part of an alias. If DEVTOOLS is populated and it implies "cmd/gcc" and "cmd/gdb", attempting to remove either component will result in an error. See examples below for how to work around this. OPTIONS
EXAMPLESWhen cloning a product, it is possible to clone a subset of it by specifying one or more component names or aliases. That will clone just that subset: Note that the list of what is "here" takes two forms, how you specified it (typically one or more aliases), and the set of components implied by those aliases. To get the second form: If you need to add something, you just tell bk populate to do that: If you need to remove something, you can only remove what you added, not individual components: If you absolutely must remove a subset, you can do so by exploding the alias in question into components: If you want to check where missing components can be found: This shows that the missing bin component has unique work in it relative to other searched repositories. In this case, in order for populate to work, the user would need to specify -@URL to name where to fetch the bin component. If you want to see all places this repository can find the missing components, add -a to the command:
CATEGORYNested
|