Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 29 Sep 2005 10:01:12 -0500
From:      Eric Schuele <e.schuele@computer.org>
To:        Roman Neuhauser <neuhauser@sigpipe.cz>
Cc:        ports@freebsd.org, Brian Kee <brianakee@gmail.com>
Subject:   Re: Need help with patching a file in a new port....
Message-ID:  <433C01B8.9020403@computer.org>
In-Reply-To: <20050929063234.GA397@isis.sigpipe.cz>
References:  <433B558D.8000204@computer.org>	<34bd754105092820056ab6f73d@mail.gmail.com>	<433B6870.7070802@computer.org> <433B558D.8000204@computer.org> <20050929063234.GA397@isis.sigpipe.cz>

next in thread | previous in thread | raw e-mail | index | archive | help
Roman Neuhauser wrote:
> # e.schuele@computer.org / 2005-09-28 21:46:37 -0500:
> 
>>I'm having slight difficulty creating a patch for a file in a new port....
>>
>>I have unpacked the source.  It merely needs a path changed in the 
>>Makefile.  So I fixed it, and created a port for it.  However, the patch 
>>I made fails to apply.  I get the message:
>>
>>  "File to patch: "
> 
> 
> # e.schuele@computer.org / 2005-09-28 23:07:12 -0500:
> 
>>The first two lines of my patch-* file (presently, after some messing 
>>around) look like:
>>  --- foo-0.1.1/src/Makefile.orig	Fri Apr  8 07:17:10 2005
>>  +++ foo-0.1.1/src/Makefile	Wed Sep 28 21:14:29 2005
> 
> 
>     Those paths are relative to the directory where patch(1) will be
>     running. That's ${PATCH_WRKSRC} (same as ${WRKSRC} by default) in
>     ports. BTW, ${WRKSRC} normally is the top directory in the tarball.
> 
>     I'd venture a guess that you need to strip the "foo-0.1.1/" from
>     the patch paths. There are knobs to coerce third party patches that
>     aren't relative to ${WRKSRC}, but it's a patch *you* are creating,
>     so there's no need to complicate the Makefile.

Ok... got it.  That straightened it out.
Thanks!

> 
> 
>>oh... I'm not determined to be the maintainer of the port... but listed 
>>myself as such since that's what the instructions said to do.  I'm 
>>willing to be... just didn't know if it was supposed to be *me* or some 
>>committer.  Guess that gets straightened out when I submit it?
> 
> 
>     It's supposed to be you.
> 


-- 
Regards,
Eric



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?433C01B8.9020403>