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
|
Notes for svn-buildpackage
==========================
svn-inject, svn-upgrade and svn-buildpackage are documented in their
manpage and in the HOWTO manual. Please refer to them for further information.
Overview for Subversion users:
-----------------------------
The recommended repository layouts are described in the PRINCIPLES
file. This schemes are auto-detected by svn-... programs. However, you can use
any type of SVN repositories as long as they don't need any special command to
be dealt with. Specify your URLs manually in .svn/deb-layout in the working
directory if the tools didn't detect them. See CONFIG file for details.
Temporary build directories are created under build-area/PACKAGE and
orig.tar.gz files are archived in tarballs/.
"packageNAME/function" is the preferred repository layout; svn-inject
creates a such structure.
svn-upgrade and svn-buildpackage look for the "mergeWithUpstream"
property of the debian directory, which means that the files in the
trunk directory are added to pre-extracted upstream source tarball at
build time. This is practical for large packages that keep only debian
and few modifications of upstream files under revision control.
svn-inject with -o option will create the tree of such type.
svn-buildpackage can also use the 'useNativeDist' property of the debian
directory to add generated files to the source tarball using a custom
idempotent 'native-dist' target in the top level Makefile of the
package. This can be used to add the POT file for use by translators.
|
