My two ยข's » ebuild http://www.linuxaddicted.de/blog A Gentoo addict, linux admin and developer Wed, 31 Mar 2010 12:12:47 +0000 en hourly 1 http://wordpress.org/?v=3.0.1 Portage: Patch existing Perl module ebuild by using a overlay http://www.linuxaddicted.de/blog/2008/12/10/portage-patch-existing-perl-module-ebuild-by-using-a-overlay/ http://www.linuxaddicted.de/blog/2008/12/10/portage-patch-existing-perl-module-ebuild-by-using-a-overlay/#comments Wed, 10 Dec 2008 19:19:09 +0000 daniel http://www.linuxaddicted.de/blog/?p=173 You may have had the same issue as i some time ago. You install a perl module from Portage but you have to modify the module’s code. Of course you don’t want to patch and install manually. Assuming the module is named “foobar” here’s how i solved it:

Create a Portage Overlay (refer . . . → Read More: Portage: Patch existing Perl module ebuild by using a overlay]]> You may have had the same issue as i some time ago. You install a perl module from Portage but you have to modify the module’s code. Of course you don’t want to patch and install manually. Assuming the module is named “foobar” here’s how i solved it:

  1. Create a Portage Overlay (refer to the official documentation) and enable it in /etc/make.conf
  2. Create a new category directory within your overlay dir (mkdir /usr/local/portage/my-ebuilds)
  3. Create application directory (mkdir /usr/local/portage/my-ebuilds/foobar)
  4. Copy the existing ebuild to the new app directory
  5. Create a files directory and put the patch there
  6. Modify the ebuild to apply your patch
...
 
# This is the magic line:
PATCHES="${FILESDIR}/my_patch.patch"
 
...

After you finished these tasks you have to (re)generate the Manifest:

ebuild [OVERLAY_PATH]/my-ebuilds/foobar/foobar-1.0.0.ebuild digest

That’s it. If you have trouble feel free to contact me: daniel@linuxaddicted.de

]]> http://www.linuxaddicted.de/blog/2008/12/10/portage-patch-existing-perl-module-ebuild-by-using-a-overlay/feed/ 0