Date: Wed, 18 Nov 2015 01:13:31 -0800 From: Yuri <yuri@rawbw.com> To: "ports@freebsd.org" <ports@freebsd.org> Subject: Ports with LOCAL/xxx as a MASTER_SITE Message-ID: <564C413B.5040602@rawbw.com>
next in thread | raw e-mail | index | archive | help
I came across a few ports like this. Most recently www/npm. It usually turns out that some slightly modified version of sources is kept there @ LOCAL/xxxx. Why not just have the patches under files/ do the modification, so that it is public and reproducible? There are also GitHub and Bitbucket, among other places, to keep sources. There should be no need to allow LOCAL/xxx as a MASTER_SITE nowadays. I suggest to abolish this practice. Begin with adding a warning to the port infrastructure when LOCAL/xxx is specified. (It makes it more difficult to suggest the patch to such port, because outsiders should first "reverse-engineer" the patches, which should have been there in files/ in the first place.) Yuri
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?564C413B.5040602>