AKA Hack-a-port
Documenting the workflow I've established to hack ports
Contents
WORK IN PROGRESS - INCOMPLETE - YMMV
Setup
Setting up your porting environment
Tools required
devel/git : Minimized depedencies CONTRIB=off CVS=off GUI=off NLS=off P4=off
ports-mgmt/portlint : Sanity checks
ports-mgmt/poudriere : To generate logs that reviewers like
One-time setup
Get a GitHub account
Create a ports repo in your GitHub
Clone your GitHub ports repo on your local system to <ghports>
Install and configure ports-mgmt/[[#poudriere|poudriere]]
Workflow
A way to get from patching a port to submitting it
Hack a port
Update the port's files.
Quality checks
portlint -C
make check-plist
make -V CPE_STR
- Build your modified port using poudriere testport
Submit a Bug Report
- If you're the maintainer of the port, prefix the Summary with [MAINTAINER] otherwise prefix with [PATCH]
e.g. [PATCH] category/port: Fix this and that
- Describe what's changed, refer to link if you submitted it upstream as well
- Attach the git diff(s)
Set maintainer-approval to + if you're the maintainer of the port
- Attach the poudriere testport log
As plain text when < 1MB
Gzipped when > 1MB
Tips-'n-tricks
make makepatch
make makepatch is your friend
- make a backup of the files dir...
run make do-patch to extract and patch the port (but not run pre- nor post-patch)
- cd into the ${WRKSRC}
Copy the file you want to modify to <file>.orig
cd `make -V WRKSRC`
cp -p path/to/file-to-patch{,.orig}Edit path/to/file-to-patch using your favourite editor
cd into the port-dir (i.e. cd ../..) run make makepatch to update all patches in the files dir
- NB. There can also be PATCH commands in the Makefile and extra-patches...
Verbose builds
Not all builds are equally verbose. Options to enable more verbose builds
make V=1 (generic)
make VERBOSE=1 (cmake)
poudriere
TODO
TODO
Poudriere usage