/usr/portsnap vs. /var/db/portsnap

[Colin Percival]

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.
> 
> 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

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.  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.

In any event, those are fairly irrelevant: I'm not going to prevent people
from running their own portsnap builds, and if someone wants the code they
can have it.

Colin Percival