Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
L
libvirt
Manage
Activity
Members
Labels
Plan
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Libvirt Packaging Team
libvirt
Commits
9c2333a8
Commit
9c2333a8
authored
8 years ago
by
Guido Günther
Browse files
Options
Downloads
Patches
Plain Diff
README.source: use gbp's boilerplate
parent
a790aa02
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
debian/README.source
+21
-49
21 additions, 49 deletions
debian/README.source
with
21 additions
and
49 deletions
debian/README.source
+
21
−
49
View file @
9c2333a8
This package
uses quilt to manage all modifications to the upstream
source. Changes are stored in the source package as diffs i
n
debian/patches and applied during the build
.
This package
is maintained with git-buildpackage(1). It follows DEP-14
for branch naming (e.g. using debian/sid for the current versio
n
in Debian unstable)
.
To configure quilt to use debian/patches instead of patches, you want
e
it
her to export QUILT_PATCHES=debian/patches in your environment
or use this snippet in your ~/.quiltrc:
It uses pristine-tar(1) to store enough information in git to generate
b
it
identical tarballs when building the package without having
downloaded an upstream tarball first.
for where in ./ ../ ../../ ../../../ ../../../../ ../../../../../; do
if [ -e ${where}debian/rules -a -d ${where}debian/patches ]; then
export QUILT_PATCHES=debian/patches
fi
done
When working with patches it is recommended to use "gbp pq import" to
import the patches, modify the source and then use "gbp pq export
--commit" to commit the modifications.
To get the fully patched source after unpacking the source package, cd to
the root level of the source package and run:
The changelog is generated using "gbp dch" so if you submit any
changes don't bother to add changelog entries but rather provide
a nice git commit message that can then end up in the changelog.
quilt push -a
It is recommended to build the package with pbuilder using:
The last patch listed in debian/patches/series will become the current
patch.
gbp builpackage --git-pbuilder
To add a new set of changes, first run quilt push -a, and then run:
For information on how to set up a pbuilder environment see the
git-pbuilder(1) manpage. In short:
quilt new <patch>
DIST=sid git-pbuilder create
gbp clone https://anonscm.debian.org/git/pkg-libvirt/libvirt.git
cd libvirt
gbp buildpackage --git-pbuilder
where <patch> is a descriptive name for the patch, used as the filename in
debian/patches. Then, for every file that will be modified by this patch,
run:
quilt add <file>
before editing those files. You must tell quilt with quilt add what files
will be part of the patch before making changes or quilt will not work
properly. After editing the files, run:
quilt refresh
to save the results as a patch.
Alternately, if you already have an external patch and you just want to
add it to the build system, run quilt push -a and then:
quilt import -P <patch> /path/to/patch
quilt push -a
(add -p 0 to quilt import if needed). <patch> as above is the filename to
use in debian/patches. The last quilt push -a will apply the patch to
make sure it works properly.
To remove an existing patch from the list of patches that will be applied,
run:
quilt delete <patch>
You may need to run quilt pop -a to unapply patches first before running
this command.
-- Guido Günther <agx@sigxcpu.org>, Wed, 2 Dec 2015 18:51:15 +0100
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment