Date: Thu, 19 Nov 2015 17:27:38 -0800 From: "Chris H" <bsd-lists@bsdforge.com> To: <freebsd-ports@freebsd.org> Subject: Re: Ports with LOCAL/xxx as a MASTER_SITE Message-ID: <a42a57ef76078e2a7b150c55c21969bb@ultimatedns.net> In-Reply-To: <564C413B.5040602@rawbw.com> References: <564C413B.5040602@rawbw.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 18 Nov 2015 01:13:31 -0800 Yuri <yuri@rawbw.com> wrote > 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.) I'd have to disagree. It's used for other things, as well. In fact, most of my experience with it, has been that someone with a commit bit, is often hosting the source it self. My .02ยข on the matter, anyway. > > Yuri > --Chris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a42a57ef76078e2a7b150c55c21969bb>