Date: Tue, 03 Jan 2017 10:58:56 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 215726] [Patch] [RFE/feature request] allow an external patches directory for 3rd party patches. Message-ID: <bug-215726-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D215726 Bug ID: 215726 Summary: [Patch] [RFE/feature request] allow an external patches directory for 3rd party patches. Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Keywords: patch Severity: Affects Only Me Priority: --- Component: Ports Framework Assignee: portmgr@FreeBSD.org Reporter: julian@FreeBSD.org CC: freebsd-ports-bugs@FreeBSD.org Keywords: patch Created attachment 178469 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D178469&action= =3Dedit diff against current ports The reason for this is to allow a complete set of patches for a project to = be held in a 3rd party repository on some unnamed source control system and applied as a single set. Possibly within poudriere. (I have not looked at s= ynth but it should wok the same) Having to apply the .local patches by hand in different directories gets too complex too fast. Being able to set an environment variable to specify the patche set to apply simplifies incorporating the ports and packages into a 3rd party product. to quote the patch: +# EXTRA_PATCH_TREE - where to find extra 'out-of-tree' patches +# Points to a directory hierarchy with the same layout +# as the ports tree, where local patches can be found. +# This allows a third party to keep their patches in +# some other source control system if needed. Does nothing if not defined. See the attached patch which had not changed in several years. (except line numbers). --=20 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-215726-13>