svn commit: r351554 - head/Mk

Steve Wills swills at freebsd.org
Fri Apr 18 17:47:43 UTC 2014


Thanks! I have run into that too. I wonder about the case of doing makepatch on
an existing port and not knowing that you needed to delete a patch. Would it be
a good idea to emit a warning or something when you would have generated an
empty patch?

Steve

On Fri, Apr 18, 2014 at 05:31:13PM +0000, Pawel Pekala wrote:
> Author: pawel
> Date: Fri Apr 18 17:31:12 2014
> New Revision: 351554
> URL: http://svnweb.freebsd.org/changeset/ports/351554
> QAT: https://qat.redports.org/buildarchive/r351554/
> 
> Log:
>   makepatch: don't create empty patches
>   
>   PR:		ports/188764
>   Submitted by:	myself
>   Approved by:	portmgr (bdrewery)
> 
> Modified:
>   head/Mk/bsd.port.mk
> 
> Modified: head/Mk/bsd.port.mk
> ==============================================================================
> --- head/Mk/bsd.port.mk	Fri Apr 18 17:28:40 2014	(r351553)
> +++ head/Mk/bsd.port.mk	Fri Apr 18 17:31:12 2014	(r351554)
> @@ -1194,6 +1194,7 @@ makepatch:
>  		for i in `find . -type f -name '*.orig'`; do \
>  			ORG=$$i; \
>  			NEW=$${i%.orig}; \
> +			cmp -s $${ORG} $${NEW} && continue; \
>  			OUT=${FILESDIR}`${ECHO} $${NEW} | \
>  				${SED} -e 's|/|__|g' \
>  					-e 's|^\.__|/patch-|'`; \


More information about the svn-ports-all mailing list