This is an old revision of the document!
This guide refers to an unofficial pkgsrc mirror on github which appears to have fallen out of date. The official git.minix3.org repositories should be used instead. The instructions need to be updated.
This makes your repositories similar, so that updates will be quick.
1. Download your pkgsrc repository
First, download the official pkgsrc.
cd /usr make pkgsrc
Then, add your remote repository.
cd /usr/pkgsrc git remote add me email@example.com:you/pkgsrc.git
2. Create your minix-master branch
git fetch me git branch my-minix-master me/minix-master
3. Check-out your minix-master branch locally
git checkout my-minix-master
Found something in pkgsrc that you want to port to MINIX?
git checkout -b my-package
# cd /usr/pkgsrc/pkgtools/pkgdiff # bmake install
This installs several tools we'll be using.
cd /usr/pkgsrc/[category]/[package] bmake patch
This applies patches, but doesn't build. Build results aren't usable for patches.
cd /usr/pkgsrc/work/[category]/[package]/work/[package name]
Use EDITOR=nano pkgvi to use GNU nano instead of nvi.
mkpatches rm patches/*.orig
bmake clean bmake
cd /usr/pkgsrc/[category]/[package] git add distinfo patches git commit
The commit message should provide a summary of the change. The first line of the commit message should be in the form “[category]/[package]: summary of change.” Example: “print/ghostscript: add missing bsd.prefs.mk include”. If it's a complex change, the commit message should provide additional explanation.
Push this branch to your remote repository.
git push me my-package
This will let others test your changes and later include them in pkgsrc.
When your branch is ready, let people know by posting to the Google Group.
Here's an example:
Subject: [package] Ported Hi, I've ported [package], and my branch "my-package" is ready for testing at: https://github.com/[me]/pkgsrc.git Thanks
When the MINIX team agrees that the package changes in your GitHub repository, they will copy the changes into MINIX's pkgsrc repository.
As changes in MINIX's pkgsrc repository become available, updating your repository allows your changes to merge cleanly in the future.
1. Update the official branch
git checkout minix-master cd /usr make pkgsrc-update
2. Make your minix-master branch identical to the official one
cd /usr/pkgsrc git checkout my-minix-master git rebase minix-master
3. Merge changes from either the official into your own
git checkout my-package-port git merge my-minix-master
4. Push your local branch up to your repository
git push me my-package
Please do your best to let people know what's happening. If you're having trouble or have an idea, then please tell someone.
The IRC channel and the Google Group are the best places for talking with the rest of the community.
If you use HTTPS and have an SSL-related problem when you fetch, then please use the following steps to install SSL certificates.
cd /usr/pkgsrc/security/mozilla-rootcerts bmake install cd /usr/pkg/etc/openssl/certs mozilla-rootcerts extract mozilla-rootcerts rehash