Notes on setting up void packages and building from source.
Fork the Void Packages repo on github if you haven’t already.
Clone your fork locally (mine is at https://github.com/sww1235/void-packages and usually exists locally at ~/Projects/src/github.com/sww1235/void-packages).
cd into your local git repo and add the upstream repo git remote add upstream git@github.com:void-linux/void-packages.git. This . This allows you to run git checkout master and then git pull --rebase upstream master to bring your local master branch up to date with the master void linux repository.
make sure your local master is up to date, then start a new branch to make your contributions in.
cd into local git repo of void-packages and run ./xbps-src binary-bootstrap. This . This will initialize the packages necessary for building software.
To enable both custom contributions to void-packages, and building modifiedsoftware with patches, use a separate git branch to actually build your custom packages from. I use a branch called build-branch-$hostname created with git checkout -b build-branch-$hostname. Whenever you want to build your custom software, checkout that branch first. I use a branch per hostname to enable unique changes per machine. This is especially important for suckless software such as dwm.
A side effect of using a custom build-branch-$hostname is that all custom changes will have full git history and can be easily applied without having to go through all the effort of rebuilding the patch files.
patches are stored in srcpkgs/<pkgname>/patches
To install custom software from a branch, need to use –repository=hostdir/binpkgs/$branch
void-linux, void-packages, source, building