File: README.source

package info (click to toggle)
kopano-webapp-plugin-files 2.1.5%2Bdfsg1-1
  • links: PTS, VCS
  • area: main
  • in suites: buster
  • size: 16,540 kB
  • sloc: php: 15,863; xml: 494; java: 295; python: 72; sh: 44; makefile: 11
file content (54 lines) | stat: -rw-r--r-- 1,922 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
+----------------------+
| embedded code copies |
+----------------------+

kopano-webapp-plugin-files comes originally with the following included code
copies.

 php/Files/Backend/Webdav/sabredav/vendor/sabre/dav
 php/Files/Backend/Webdav/sabredav/vendor/sabre/vobject

These two folders are cleaned out while importing the code by gbp or also by
using uscan via Files-Excluded. As both PHP components are needed we symlink
that needed folders to existing packages inside Debian main.

There is one more embedded code which we unfortunately can't exclude as the
component isn't packaged for Debian yet.

 php/lib/phpfastcache

-------------------------------------------------------------------------------

+-----------------+
| DFSG compliance |
+-----------------+

Upstream is also shipping a flash file which we don't have sources for.

 resources/flash/charts.swf

We also exclude that file while importing. Due this we add a '+dfsg$(number)'
to the *orig.tar.xz to mark the file as dfsg cleaned out.

-------------------------------------------------------------------------------

+--------------------------------------+
| kopano-webapp-plugin-files packaging |
+--------------------------------------+

The kopano-webapp-plugin-files packaging is maintained by git-buildpackage.
This means the whole Debian specific work is done in separate branches as
described in DEP-14. The package also use pristine-tar for storing delta data
to always reproduce bit by bit identical source tarballs.

The preferred way to work on patches is by using the ability of
git-buildpackage to handle a separate branch for patch queue content. Just
import the current patches (if needed) by importing them by git-buildpackage.

  $ gbp pq import
  # modify and adopt the patches as single commits
  # once ready export the patches
  $ gbp pq export


 -- Carsten Schoenert <c.schoenert@t-online.de>, Wed, 3 Oct 2017 14:10:00 +0200