aboutsummaryrefslogtreecommitdiff
path: root/bpkg/package.hxx
diff options
context:
space:
mode:
authorKaren Arutyunov <karen@codesynthesis.com>2018-05-10 21:28:26 +0300
committerKaren Arutyunov <karen@codesynthesis.com>2018-05-10 21:28:26 +0300
commitca387611165403835655db1f3620ef8e65cb92b5 (patch)
treeb0b7c0a3d0b019edbf2bc8e4e573d082d8068bdb /bpkg/package.hxx
parent51b35a2d4305a2f302be62a370c4b00b2a215279 (diff)
Fix package checksum mismatch for all repositories being fetched
Diffstat (limited to 'bpkg/package.hxx')
-rw-r--r--bpkg/package.hxx10
1 files changed, 2 insertions, 8 deletions
diff --git a/bpkg/package.hxx b/bpkg/package.hxx
index 1986e1f..94d5136 100644
--- a/bpkg/package.hxx
+++ b/bpkg/package.hxx
@@ -247,17 +247,11 @@ namespace bpkg
// fragmented. For example, a git repository consists of multiple commits
// (fragments) which could contain different sets of packages and even
// prerequisite/complement repositories. Note also that the same fragment
- // could be shared by multiple repository objects. We assume a fragment to
- // be immutable, so it's complement, prerequisite and package sets can never
- // change.
+ // could be shared by multiple repository objects.
//
// For repository types that do not support fragmentation, there should
// be a single repository_fragment with the name and location equal to the
- // ones of the containing repository. Such a fragment can not be shared but
- // can be changed.
- //
- // One of the consequences of the above is that a fragment can either be
- // shared or be mutable.
+ // ones of the containing repository. Such a fragment cannot be shared.
//
class repository;