You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current documentation only covers applying a patch, which is of little help if the packager doesn't first know how to make a patch file in the first place.
The section should include the following steps:
Clone the source repository
Make changes to the source
Create the patch file
i. Create a git commit detailing the changes
ii. Create (if not exists) the files directory inside the package's directory
iii. Run git format-patch -o ~/path/to/package/dir/files to create the patch file
The text was updated successfully, but these errors were encountered:
Adding Reilly's suggested improvement here before I forget:
If you use git format-patch with the arguments --zero-commit and --no-signature it'll zero out the commit hash and strip the git version from the bottom
This can help reduce the diff from updating the patches in the future a bit
The current documentation only covers applying a patch, which is of little help if the packager doesn't first know how to make a patch file in the first place.
The section should include the following steps:
i. Create a git commit detailing the changes
ii. Create (if not exists) the
files
directory inside the package's directoryiii. Run
git format-patch -o ~/path/to/package/dir/files
to create the patch fileThe text was updated successfully, but these errors were encountered: