Most ebuilds here are experimental and will move to ::science if they are stable and relevant.
$ git add
$ pkgdev commit
$ pkgdev manifest
Usually I follow these steps (I use less package as example)
- unpack package ebuild /usr/portage/sys-apps/less/less-531.ebuild unpack;
- duplicate source code cp -r /var/tmp/portage/sys-apps/less-531/work/less-531/ /var/tmp/portage/sys-apps/less-531/work/less-531.orig
- go in to source directory cd /var/tmp/portage/sys-apps/less-531/work/less-531/ and change necessary files
- go in work directory cd /var/tmp/portage/sys-apps/less-531/work/
- and finally create patch diff -Naru less-531.orig less-531 > your_patch_files.patch
Is a chaos monkey approach to keep checking the relevant packages.