On Sun, 16 Nov 2008 19:16:26 -0600 Harry Putnam wrote: > After looking at: > http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=2&chap=1#doc_chap2 > > [ Ebuild HOWTO ] > > Reading only partially so far but this looks really complicated. I > thought I remembered a more nuts and bolts howto somewhere more > appropriate for someone getting started who is ..er intellectually > challenged. > > I really just want to add an epatch line to an existing ebuild but it > appears some protocols need to be followed to generate the manifest > and probably lots of other stuff. > > Can anyone point me to something? > > I've see it said here a few times that creating an overlay and a > custom ebuild is `easy' but I suspect that only applies if you already > know how its done. >
I've created a couple of patch ebuilds, so can provide some (non-expert) info. I don't recall all the steps I took to get "educated" in this process, but I remember looking at a variety of ebuilds, the patterns in their names (what's legal), and the commands used within them. For "system/package" (for example mail-filter/bogofilter) one would 1) create directory /usr/local/portage/system/package and copy /usr/portage/system/package/* to it. 2) put the patch file in /usr/local/portage/system/package/files/ 3) create a new ebuild (with updated version) and an epatch line in src_install() 4) update the manifest file with ebuild system/package/package-version.ebuild digest Obviously these instructions are somewhat minimal. You'll likely need to run "emerge package" more than once to get the details right. HTH, David
