File: README.source

package info (click to toggle)
borgbackup2 2.0.0b19.post2-3
  • links: PTS, VCS
  • area: main
  • in suites: forky
  • size: 31,340 kB
  • sloc: python: 31,228; pascal: 3,510; sh: 216; makefile: 156; tcl: 94; ansic: 21
file content (18 lines) | stat: -rw-r--r-- 1,030 bytes parent folder | download | duplicates (4)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
This supposedly is a standard gbp package not deviating from defaults where it
doesn't have to. When it does deviate, that's probably unintentional. Consider
using `dgit --quilt=gbp push-source` for uploading.

Due to borg 1.x and borg 2.x being incompatible and being a networked
application, we allow coinstallation during bookworm. This is implemented using
the `*-is-*` pattern pioneered by python. Deviating from it, borgbackup
implicitly serves the role of the non-existent package
`borgbackup-is-borgbackup1`. `borgbackup2` only contains versioned tools and
`borgbackup-is-borgbackup2` only contains symbolic links. Reverse dependencies
compatible with both borg versions should `Depends: borgbackup-is-borgbackup2 |
borgbackup`.

In agreement with upstream, the Python module has been moved to a private path.
This serves two purposes:
 * The module is not meant to be imported except by upstream. Its API is not
   considered stable. Users should use the CLI instead.
 * Moving the module is required for coinstallation.