aboutsummaryrefslogtreecommitdiff
path: root/bpkg/repository-types.cli
diff options
context:
space:
mode:
Diffstat (limited to 'bpkg/repository-types.cli')
-rw-r--r--bpkg/repository-types.cli6
1 files changed, 4 insertions, 2 deletions
diff --git a/bpkg/repository-types.cli b/bpkg/repository-types.cli
index ad8f09d..1692a13 100644
--- a/bpkg/repository-types.cli
+++ b/bpkg/repository-types.cli
@@ -32,7 +32,7 @@ cannot be guessed from the URL. See \l{bpkg-rep-add(1)} for details.
A \cb{pkg} repository is \i{archive}-based. That is, it contains a collection
of various packages/versions as archive files. For more information on the
structure of \cb{pkg} repositories refer to \l{bpkg The \cb{build2} Package
-Manager Manual}. The \cb{dir} repository location can be a local directory
+Manager Manual}. The \cb{pkg} repository location can be a local directory
path or an \cb{http(s)://} URL.
@@ -189,7 +189,9 @@ that they support fetching minimal history for tags and branches and may or
may not support this for commit ids depending on the server configuration.
Note, however, that unlike for \cb{http(s)://}, for these protocols \cb{bpkg}
does not try to sense if fetching unadvertised commits is allowed and always
-assumes that it is not.
+assumes that it is not. Also note that the sensed or assumed protocol
+capabilities can be overridden for a \cb{git} repository URL prefix using the
+\cb{--git-capabilities} option (\l{bpkg-common-options(1)}).
Based on this information, to achieve optimal results the recommended protocol
for remote repositories is smart \cb{https://}. Additionally, if you are