rpm/qemu
SHA256
1
0
Fork 0
forked from pool/qemu
Code Pull Requests Activity

Accepting request 731688 from home:bfrogers:branches:Virtualization

Browse Source 
Tweak cross compiler used based. Also clean up commentary in scripts.

OBS-URL: https://build.opensuse.org/request/show/731688
OBS-URL: https://build.opensuse.org/package/show/Virtualization/qemu?expand=0&rev=488
This commit is contained in:
Bruce Rogers
2019-09-18 08:58:50 +00:00
committed by Git OBS Bridge
parent 64435eabdc
commit 3ab58a2291
6 changed files with 32 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
README.PACKAGING
View File

@@ -15,11 +15,11 @@ first run pkg2git.sh, in order to get the current patch queue made available in
a local git branch named frombundle. (qemu packaging now includes a "bundle of
git bundles" stored as a package source file, which contains the "git version"
of the package patches.) You will create an altered patch queue in the
$GIT_BRANCH branch (see config.h for actual name), and use the frombundle branch
as a starting point (eg perhaps start by doing git reset frombundle, then cherry
-pick upstream patches from there). Once you have the patch queue ready to go
run git2pkg.sh to update the bundle of bundles (bundles.tsr.xz file) as well as
the spec and patch files.
$GIT_BRANCH branch (see config.sh for actual name), and use the frombundle branch
as a starting point (eg perhaps start by doing git reset --hard frombundle, then
cherry-pick upstream patches from there). Once you have the patch queue ready to
go run git2pkg.sh to update the bundle of bundles (bundles.tsr.xz file) as well
as the spec and patch files.
Additional Notes:
@@ -62,8 +62,8 @@ This will cause the patch application in the spec file to be done as follows:
%patch0013 -p1
%endif
A track worth noting is, if a given git tracked patch is to be applied in a way
that can't be done in the normal patching section of the specfile, you can still
A trick worth noting is, if a given git tracked patch is to be applied in a way
that can't be done in the normal patching section of the spec file, you can still
include the patch, and use it by name with the patch program elsewhere in the
spec file by doing something such as:
Include-If: %if 0%{?patch-possibly-applied-elsewhere}