1
Notes on the pymca source package for Debian
2
============================================
7
These sources are packaged in the standard '3.0 (quilt)' dpkg source
8
format. The patches in 'debian/patches' are generated from the package
9
git repository (see the Vcs-Git field in debian/control) by diffing
10
the 'upstream' branch with the patch branch ('p/*').
12
Making a change to the package sources does not require working with the git
13
repository. The package can be changed in a normal way by either adding a new
14
patch to 'debian/patches' or by changing the sources directly and letting
15
dpkg-source build the additional patch during source package creation.
17
Working with the packaging git repository
18
-----------------------------------------
20
The 'master' branch of the git repository always contains the complete patched
21
sources, ready to be built by 'debuild -i\.git' or a similar command.
22
Commits modifying the upstream sources should go to the master branch
23
and also be cherry picked to a specific patch branch, in order to be
24
included in a separate patch file in the source package. Upstream modifying
25
commits not included in any of the patch branches will be placed by
26
dpkg-source to the catchall patch 'debian/patches/debian-changes-{version}',
27
but having this patch in a released version is discouraged.
29
The generated patches and the order of patch application are determined
30
by DEP-3 header information files in 'debian/metapatches', with file names
31
having the format 'nn_patchname'. The number 'nn' determines the order of the
32
patch in the series. An extra header field 'X-git-branch' in the
33
metapatch file points to the git branch used to generate the patch file.
35
Some scripts to automate the patch and series file generation and other tasks
36
can be found at http://gitorious.org/gdp
added
removed
debian/README.source
