Date: Mon, 15 Jun 2015 08:21:06 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 200428] [patch] allow custom PATCH_PATH_SEPARATOR defined in port Message-ID: <bug-200428-13-hN6gCk9DH1@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-200428-13@https.bugs.freebsd.org/bugzilla/> References: <bug-200428-13@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200428 --- Comment #5 from Mathieu Arnold <mat@FreeBSD.org> --- (In reply to Olli Hauer from comment #4) > The issue I'm talking about is not for existing patches, it is for new ones. > > In case the file or path contains '_' the resulting patch file name is > nonsense. > > E.g. original file path is ${WRKSRC}modules/ssl/ssl_engine_init.c > > cd www/apache24 > > make patch > > rm files/patch-modules__ssl__ssl_engine_init.c > > make makepatch > > > svn stat files/ | grep init.c > ! files/patch-modules__ssl__ssl_engine_init.c > ? files/patch-modules_ssl_ssl__engine__init.c Ok, as it is an existing patch, have you tried not rm'ing the file before running makepatch ? If you *do not* rm the existing patches before running makepatch, it should put the patches in the current file and not in the new canonical name. If *that* is not working correctly, please tell us. Now, the canonical name of a patch, is _ is replaced by __ and / is replaced by _. -- You are receiving this mail because: You are on the CC list for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-200428-13-hN6gCk9DH1>