File: README.source

package info (click to toggle)
postbooks 4.9.5-1~bpo8%2B1
  • links: PTS, VCS
  • area: main
  • in suites: jessie-backports
  • size: 103,120 kB
  • sloc: cpp: 288,269; sh: 607; xml: 214; awk: 104; makefile: 49
file content (53 lines) | stat: -rw-r--r-- 1,883 bytes parent folder | download | duplicates (4)
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

-- NMUs are welcome, but... --

NMUs are welcome.  If you contribute to this package, either by
making an NMU or as a participant in the pkg-xtuple packaging team,
please:

a) commit your work to Git, don't leave it for somebody else to do
b) when your package upload is accepted, tag the commit that you used
   to build the package
c) don't forget to push your commits and tags to alioth
d) if you patched upstream code, send the patch to upstream using a
   Github pull request or email

For more details about the team, please see:

    https://alioth.debian.org/projects/pkg-xtuple/

Our repositories are in collab-maint so you don't need to be a member
of the pkg-xtuple team on alioth before committing to the repositories.

-- Following upstream repositories --

Due to the nature of Git, we have cloned the upstream repositories,
we do the Debian work in branches and we push our branches to alioth.

The upstream developers are active on Github, they use Ubuntu
themselves and they welcome collaboration with the Debian and Ubuntu
communities.  Therefore, anybody making patches against this package
should submit their patch to upstream using a Github pull request or an
email so that we won't have to maintain them under debian/patches

--- Disk space ---

A build of this source package appears to require about 2.5GB


--- Icon ---

The icon (xTuple.xpm) was created from guiclient/xTuple.ico by
using gimp to scale it to 32x32 and save it as an xpm file
in accordance with Debian menu policy.

-- Legacy comments concerning tarballs on Sourceforge --

Before September 2015, we would use the upstream tarballs from
Sourceforge or Github, repacking them and putting them in
an independent packaging repository.

Use the script debian/repack-postbooks.sh for repacking the
upstream tarballs.  They frequently come with binary artifacts
from the packaging environment.