From owner-freebsd-ports Sat Dec 28 19:42:55 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id TAA11591 for ports-outgoing; Sat, 28 Dec 1996 19:42:55 -0800 (PST) Received: from ingenieria ([168.176.15.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id TAA11571 for ; Sat, 28 Dec 1996 19:42:40 -0800 (PST) Received: by ingenieria (SMI-8.6/SMI-SVR4) id WAA00607; Sat, 28 Dec 1996 22:29:31 -0500 Date: Sat, 28 Dec 1996 22:29:30 -0500 (EST) From: Pedro Giffuni To: Satoshi Asami cc: ports@freebsd.org Subject: Re: Questions about a ports freeze... In-Reply-To: <199612290058.QAA16337@baloon.mimi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-ports@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Thanks for the answer, we are not on freeze but it's interesting to know this. On Sat, 28 Dec 1996, Satoshi Asami wrote: > * 1) Is /pub/FreeBSD/incoming/ cleaned towards the end of freezes, after a > * port is comitted, or is it never cleaned? > > It is supposed to be cleaned after a port is committed. But sometimes > the committer never gets around to it. And then once in a while we > get a massive warez (or whatever) attack and the sysadmin cleans up > everything. > Perhaps incomming should be clean both after commiting and after the ports freeze (by cleaned I also mean properly treated if that's the case). Many people simply drop their ports without sending a PR and no one looks until the port is rather old. (That's the case with URT, I have almost ready a version 3.1p1, and I found a submitted 3.1 port). There were also some instructions about how to download a pirate version of Visual Basic, which is 1) illegal and 2) of little use for Fbsd users.! It's perfectly normal to have a big incoming dir (just look at sunsite!), but it is annoying to have so much garbage. best regards, Pedro. > > Satoshi >