What is the correct means to patch Wine for a personalized PPA?
I've been by hand using spots to Wine for usage on my very own equipment, yet I intend to place it in a PPA for my close friends and also relationships.
Presently I follow this procedure :
- Get the most up to date resource from an upstream PPA using
patchto use my informal, in need of support spots.
- Create a plan making use of
dpkg-buildpackage -rfakeroot -uc -b
This is great for developing a plan that will certainly work on my neighborhood equipment. Nonetheless I currently intend to disperse this personalized construct to others using a PPA.
Is this procedure enough, or exists an extra proper and/or less complicated to keep procedure I should be adhering to especially for Wine?
From the winehq internet site:
Open the Software Sources food selection by mosting likely to System - > Administration - > Software Sources. After that select the Third Party Software tab and also click Add.
After that, duplicate and also paste the line listed below.
ppa :ubuntu - wine/ppa
Then run sudo apt - get upgrade and also after it's done sudo apt - get install wine
You require to first construct a resource plan -
Pushing it to a PPA is really simple for Ubuntu 9.10 or later on
Just most likely to Terminal and also type
dput ppa:your-lp-id/ppa <source.changes>
You're rather close with your instance actions, yet below's what I would certainly recommend :
- Grab the resources with
apt-get source wineand also
cdright into the new directory site
- Find what type of patch system the wine plan is based upon :
what-patch; in this instance, it informs us we that the wine plan makes use of
quiltfor patch monitoring
- Since we're making use of patchwork, add your personalized patch (es) to the patchwork collection :
QUILT_PATCHES=debian/patches quilt import <your-patchfile.patch>If you have numerous spots, do this for each and every patch, in the order that you desire them used.
- Add an ideal access to the
debian/changelogdocuments - you'll require to modify the variation number to make certain that your PPA variation is set apart from the main variation. Commonly, you need to increment the last variation number, and also add a tilde (~) adhered to by your personalized variation string (eg
dch -icommand can aid with this also.
- Construct the resource plan :
- Upload your resource plan to the PPA construct system :
dput ppa:<your-ppa> ../wine*.changesThe
parameter is defined on the launchpad web page for the PPA you intend to upload it to (you'll need to create this ahead of time).
It's generally an excellent suggestion to do an examination construct prior to doing the dput - the
pbuilder command permits you to recreate what the PPA construct system would certainly perform with your plan (ie, begin with a tidy install, add called for deps, after that construct).
In this instance you would certainly need to set up pbuilder first (see https://wiki.ubuntu.com/PbuilderHowto), after that do this prior to the
sudo pbuilder build ../*.dsc
Jeremy's solution is straight to the factor.
Conversely, you can make use of
bzr to take care of the resource, spots and also building/upload.
See https://wiki.ubuntu.com/DistributedDevelopment, beginning with https://wiki.ubuntu.com/DistributedDevelopment/Documentation.
While is streamlines some actions, as an example combining for new upstream variations (if you intend to be successful of the initial Ubuntu plan), the initial "proper - get resource" strategy is possibly extra straight and also less complicated ultimately