Patching source before emerge (Unpacking?)

Inaba · n00b Joined: 18 Jun 2002 Posts: 16

Hi all,

I need to make a very small change to the source of one of the portage packages. I can't seem to find any documentation or posts about how to unpack the source, apply my change and then emerge the whole thing.

I know it's possible, but it's being difficult.

Currently, I changed one of the already existing patch files, and then changed the resulting MD5SUM in the verification file. This is a bad thing, and I'm not sure it even worked properly.

Any help would be appreciated.

delta407 · Posted: Tue Jun 18, 2002 3:43 pm Post subject:

Get the full filename for the ebuild, and do the following:

arkane · l33t Joined: 30 Apr 2002 Posts: 918 Location: Phoenix, AZ

474 · l33t Joined: 19 Apr 2002 Posts: 714

Another way is to modify the ebuild file itself and insert any commands as necessary to patch the source code at the end of the src_unpack subroutine. These auto-defined shell variables can be used:

${P} = Program name/source subdirectory name
${S} = Source working path (under /var/tmp/portage)

So the fully qualified path for where the source code is after unpacking is : ${S}/${P}

You can see numerous examples of this in various ebuilds (xfree, gentoo-sources, apache etc) usually using patch or sed. You won't need to modify the digest file, and you can re-emerge without having to manually do your patching. But your customised ebuild will get hosed the next time you emerge rsync unless you (a) backup or (b) use CVS instead to update the portage tree.

Inaba · n00b Joined: 18 Jun 2002 Posts: 16

Thanks for the info folks

However... I can't seem to get this to work. When I try to unpack (for example) php, it says it can't find it... even though I know the tar file is there (I went and untarr'd it myself manually just to be sure)

For example, if I do this:

cm php-4.2.1-r1 # ebuild php-4.2.1-r1.ebuild unpack
!!! No message digest file found. /var/db/pkg/dev-lang/php-4.2.1-r1/files/digest-php-4.2.1-r1
!!! Type "ebuild foo.ebuild digest" to generate a digest.

That's what I get.

If I try to use the name w/o the .ebuild, it can't find it. If I use the tgz file, says it can't find it. What am I doing wrong?

AutoBot · l33t Joined: 22 Apr 2002 Posts: 968 Location: Usually Out

You must do it this way:

AutoBot · l33t Joined: 22 Apr 2002 Posts: 968 Location: Usually Out

Oh and for packages that are masked you can do this instead of unmasking it:

scottro · Posted: Tue Sep 03, 2002 12:16 am Post subject:

I wanted to thank you people for this thread. I was trying to add a patch to mutt that enables it to send to OE users with the gpg signature in the message, rather than attached. This thread clarified the procedure for me.

Thanks again

Scott

Bigbeanpole · n00b Joined: 24 Apr 2003 Posts: 12

Would this be similiar to using an overlay directory? I've been told the basics on the procedure, and having this thread helped to clarify the procedure, however, how would I incorporate that into creating a .patch to be used in the emerge procedure?

The reason I ask is because I've been having troubles emerging avifile.... I keep getting an error that ld cannot find -lXrender, but I don't think ld is looking in the right directory. I need to modify the makefile to include the missing directory(which is located in the /etc/ld.so.conf file...but isn't being picked up for some reason).

Thoughts/suggestions on this would be greatly appreciated.

iTux · Guru Joined: 07 Sep 2004 Posts: 586 Location: Toronto

jupiter_ · n00b Joined: 08 May 2005 Posts: 1

Hi!

I can't patch an ebuild.
There is an error in an ebuild, and I've got to patch it, but if I change the .ebuild file, I get size and md5 problems, like the starter of this topic.

So I unpack the ebuild as you wrote to do. And what's next? If I change the file in the /var/tmp/portage/pack/build-info/xy.ebuild it doesn't take any effect at 'ebuild pkname compile'.

The bad ebuild I torture with is pvm-3.4.4-r2.ebuild, Bugzilla Bug 71682. Two rows is needed to insert to the file.

rusty · Posted: Thu Jul 14, 2005 6:46 pm Post subject:

To get rid of digest warnings in an ebuild:

ftwig · n00b Joined: 04 Nov 2005 Posts: 32

This thread looks like what I want but I am totaly new to patching. I am trying to patch a .ccp file from http://svn.mythtv.org/trac/changeset/7583. Do I just find the file and replace it?

davy_gravy · n00b Joined: 18 Aug 2007 Posts: 26

thanks to contributors who offered ideas here, and encouragement to those who need help patching source before emerging a package...

the overlay is the right way to go...

I needed to patch a single value in the source for gnome-nettool-2.18.0 (the port scanner in it only scans from port 1 to port 7000, and this was super easy to change in the source, just replace 7000 w/ 65535). I had actually posted this bug (original bug filed at Ubuntu and the upstreamed-bug at Gnome) more than a year back when I was working in Ubuntu, but since I needed to switch to Gentoo, I thought that now I could actually do something about it !

Although I''ve been tinkering w/ OpenEmbedded/Bitbake for a couple of months, Portage seemed to have much more sophistication... and is picky... and stuff seems like it is "all over the place"... but it does make some sense now to me. Here's how I did it.

1. My regular portage stuff is in /var/db/pkg/<category>/<package-name-ver#>/ . I made a careful note of the directory structure there, and how things were named. In particular I looked to see the path of the ebuild I needed to use:

biocyberman · n00b Joined: 22 Jun 2017 Posts: 1

Year 2017. This trhead is old, but since this thread showed up when I search "ebuild unpack only", I add this title trick to help others:
One can use

fedeliallalinea · Posted: Thu Jun 22, 2017 8:12 am Post subject:

Now for appling a patch/es to a ebuild you can use /etc/portage/patches.
_________________
Questions are guaranteed in life; Answers aren't.