Best way to handle private patches

Message

curmudgeon · Post by **curmudgeon** » Tue Feb 17, 2004 12:08 am

A couple of applications, I want to patch with my own patch before compiling
(not just on one occasion, but every time I build the application). Can someone
explain possible ways of doing this, and their advantages and disadvantages?
Any documentation (maybe something a little less comprehensive than the
ebuild howto for the developers :) ) or stories from people who have done this?
Thank you for your help.

curmudgeon · Post by **curmudgeon** » Sun Feb 22, 2004 6:34 am

No answer yet (and I can't believe no one hasn't done this before).

Hypnos · Post by **Hypnos** » Sun Feb 22, 2004 7:56 am

It's straightforward: Make an ebuild with a weird version number that does that patch during the src install phase.

If you want examples, just do "grep -r epatch /usr/portage".

TheEternalVortex · Post by **TheEternalVortex** » Sun Feb 22, 2004 8:14 am

The easiest way to do this if you only want to compile it once is to do (e.g.):

Code: Select all

# cd /usr/portage/ebuilddir
# ebuild myprog-1.0.ebuild unpack
# cd /var/tmp/portage/myprog-1.0/work/
# cp ~/mypatch.patch .
# patch -p0 < mypatch.patch
# cd -
# ebuild myprog-1.0.ebuild compile
# ebuild myprog-1.0.ebuild qmerge

Or you can make your own ebuild by copying the existing one to your portage overlay and adding a line that says epatch mypatch.patch in the unpack section.