From owner-freebsd-ports@freebsd.org Tue Aug 14 15:33:41 2018 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0379B107BAAE for ; Tue, 14 Aug 2018 15:33:41 +0000 (UTC) (envelope-from mat@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AC406751A0; Tue, 14 Aug 2018 15:33:40 +0000 (UTC) (envelope-from mat@FreeBSD.org) Received: from ogg.in.absolight.net (ogg.in.absolight.net [IPv6:2a01:678:ab:50::42:42]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: mat/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 02762C449; Tue, 14 Aug 2018 15:33:39 +0000 (UTC) (envelope-from mat@FreeBSD.org) Date: Tue, 14 Aug 2018 17:33:38 +0200 From: Mathieu Arnold To: blubee blubeeme Cc: Helen Koike , FreeBSD Ports Subject: Re: workflow question: how do you maintain the port in sync with upstream? Message-ID: <20180814153338.bujxg3a5uswj3y5n@ogg.in.absolight.net> References: <05457c2b-b85c-a929-20e7-38ff1b2899d6@collabora.com> <87211ccd-bb2f-cd03-ecde-fd123d0c9ca5@collabora.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="7npqrc57l3pg3vqf" Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20180622 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Aug 2018 15:33:41 -0000 --7npqrc57l3pg3vqf Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Aug 14, 2018 at 10:41:43PM +0800, blubee blubeeme wrote: > This one is fairly straight forward, you can simply replace that string > with a regex command; > This is an example of running a replace command for strings after the pat= ch > phase of the build; >=20 > post-patch: > @${REINPLACE_CMD} -e 's|for Linux|for FreeBSD|g' ${WRKSRC}/README Patching files in post-patch using sed SHOULD only be used to replace dynamic content, never static content. --=20 Mathieu Arnold --7npqrc57l3pg3vqf Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQKTBAABCgB9FiEEOraXidLtEhBkQLpbOkUW81GDzkgFAlty9lFfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDNB QjY5Nzg5RDJFRDEyMTA2NDQwQkE1QjNBNDUxNkYzNTE4M0NFNDgACgkQOkUW81GD zkhnJg/+Ouv1YwX93TAXZ75VNtbhhZaN2tD5GFu3aVfYjlEJpGA3ZKCiXAmX/aDt zqOBSPluVTe+Fw0ULPvRc2hMxKbFFECVlQSBl/reSMhKvUk98gnmR1uSUujHle7I ktKPUCBCO4xDIZEpTVB3ExbrDYjbLkGDm6OwzLVv76RDXOuKbv+ccD/iyrqu8uXY WllIp79+TbVsgxQt678yU3+BJ7DoTC+5nsrnHccwxGBC8/+ewI8NqjeXO0hFN2Kw D1rniBPJgW/Qsn9rYYuYzjfg+qDM8gJqCWWM/mVlrWV98F4+k0ENHdvlRtZOh7EO 4pLWI2kJmy2WD3So+XQgjysxlzcpW5Xn8mC9baBIpJJYoOi3A4D5pJ/nx7cIndFF HQKejdOZMgo5ubXr7lG/dzz+iYzn/SfPQ8haD2ngg2xp4psQkT5LQFBwP0GLrYoy k250QjRdELVNDTyYj0N9FMWHQLobpaeplnQiu7Q8zuGg8zJlLtB4hxDiIGzIu90F BFJbXCbldyEkh4wxZV9byIURS7Xjmxl93amnfG4Ls7CbGyEw+S+feQ5rQzrDoxQc /W/R9eYSPUH3C3iaBNfwPDBb8ocHfXvAgQlt1+YHbo1BMJ0tuvdi+duMTmF7OhoG 9Wnj6d18wXtcVVW+pIDGmtpPhL75WczYAsUG51nG+c4SBB4orWg= =uON1 -----END PGP SIGNATURE----- --7npqrc57l3pg3vqf--