Subject: Re: Overriding pkgsrc-supported version of a package with a newer
To: Gavan Fantom <firstname.lastname@example.org>
From: Eric Boutilier <Eric.Boutilier@Sun.COM>
Date: 03/08/2005 19:19:49
On Mon, 7 Mar 2005, Gavan Fantom wrote:
> On Fri, 4 Mar 2005, Eric Boutilier wrote:
>> So I downloaded a snapshot source tarball from snaps.php.net and
>> built it successfully by modifying Makefile.common (to recognize
>> the distfile) and emptying the patches directory. But I just
>> discovered I'm not home-free yet because anything that requires
>> PHP needs to be configured to know about my override.
> What do you mean by "needs to be configured to know about my override"?
> Does your updated php package install into a different location?
Because of the method I used, the name of the installed PHP
package was not recognizable to other packages that required
it. Instead of the installed package being named php-5.0.3, it was
named with the version number of the snapshot I downloaded from
snaps.php.net. So when I tried to build anything that depended on
it, like SquirrelMail, the build of course would not detect that
the dependency was satisfied, and would try and build php5 anyway.
Having said that, I've thought of a better process (the right
process?) for overriding a package with a development version:
Manually modifify (un-tar, modify, re-tar) the source tarball
so that it extracts into /lang/php5/work/php-5.0.3 rather than
a directory named with the development version number. I haven't
had time to try it yet though.
>> Am I going about this the wrong way? (I already realize that
>> bypassing the patches could get me in trouble...)
> The patches look like they'd probably still apply against a minor update. Was
> deleting them necessary?
I think one or more of the files that it would try to patch had
changed in the snapshot release causing it to be incompatible
with pkgsrc's corresponding patch. In any case, the patch stage
failed unless I just moved them out of the way.
> Gillette - the best a man can forget