Date: Sun, 7 Aug 2005 23:46:18 +0200 From: Stijn Hoop <stijn@win.tue.nl> To: Colin Percival <cperciva@freebsd.org> Cc: freebsd-arch@freebsd.org Subject: Re: /usr/portsnap vs. /var/db/portsnap Message-ID: <20050807214618.GG70957@pcwin002.win.tue.nl> In-Reply-To: <42F632B3.90704@freebsd.org> References: <42F5BC19.5040602@freebsd.org> <20050807.211240.75793221.hrs@allbsd.org> <42F60443.2040301@freebsd.org> <20050807.231125.26489231.hrs@allbsd.org> <42F61960.4020400@freebsd.org> <20050807160452.GF70957@pcwin002.win.tue.nl> <42F632B3.90704@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--VkVuOCYP9O7H3CXI Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Aug 07, 2005 at 09:11:31AM -0700, Colin Percival wrote: > Stijn Hoop wrote: > > On Sun, Aug 07, 2005 at 07:23:28AM -0700, Colin Percival wrote: > >>Those don't belong in src, but I could put them into the projects repo > >>if people really want them. > >=20 > > Not that I am going to do any such thing, but why prevent people from > > providing their own binaries? Maybe they want to distribute their own > > ports tree to an internal cluster using portsnap >=20 > Two reasons come to mind: First, the portsnap chain of security starts > with running cvsup to cvsup-master through a tunnel to freefall... a > non-committer wouldn't be able to do that. OK, I'm still arguing in the hypothetical case, but why is it insecure then to redistribute a copy of a portsnap'd ports tree + local patches? > Second, it would be far more > efficient for this hypothetical user to keep their modifications as a > local set of patches which were applied post-portsnap on individual > machines. That might very well be true. In any case, this is all hypothetical. All that _I_ am going to do is checkout the portsnap client when it hits the base system. So no more devil's advocate for me. And last but certainly not least: thank you for sharing your software in the first place! --Stijn --VkVuOCYP9O7H3CXI Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFC9oEpY3r/tLQmfWcRAuihAJsFhDMnq6R3hyMy3NeS8eZKWtWFFACfYSut F2FHkSs/Y84mFgMee82d8EA= =YgZH -----END PGP SIGNATURE----- --VkVuOCYP9O7H3CXI--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050807214618.GG70957>