suggested patch for bsd.ports.mk

Julian Elischer julian at freebsd.org
Sat May 14 03:25:25 UTC 2016


On 13/05/2016 12:11 AM, Julian Elischer wrote:

so who or what decides if I can put this in?  As a long term committer 
from before there were ports, do I have access to it?
do I need to get a ports mentor? (seems likely and would make sense).. 
do I apply somewhere? Or should I look for soemone in ports to do it 
for me?


> This patch is pretty self explanatory.
>
> it allows us to keep patches for various ports separately in a 
> sparse hierarchy while not having to write to the ports tree itself.
>
> In case the list scrubs hte text attachment (diff) here's the 
> description part of the diff.
>
> >==== //depot/bugatti/FreeBSD-ports-PZ/10.1/Mk/bsd.port.mk#2 (text) 
> ====
>
> @@ -791,6 +791,11 @@
>  #                  The patches specified by this variable will be
>  #                  applied after the normal distribution patches but
>  #                  before those in ${PATCHDIR}.
> +# 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.
>  # PATCH_WRKSRC    - Directory to apply patches in.
>  #                  Default: ${WRKSRC}
>  #
>
> If anyone thinks this is a good idea, I'd like it to go in as we 
> have to maintain it..
> I could commit it myself but haven't had my ports wings awarded yet..
>
>
>
>
> _______________________________________________
> freebsd-ports at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscribe at freebsd.org"




More information about the freebsd-ports mailing list