From owner-freebsd-ports@FreeBSD.ORG Wed Aug 16 16:31:24 2006 Return-Path: X-Original-To: ports@freebsd.org Delivered-To: freebsd-ports@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6663116A4DA for ; Wed, 16 Aug 2006 16:31:24 +0000 (UTC) (envelope-from infofarmer@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id 36B4E43D5A for ; Wed, 16 Aug 2006 16:31:21 +0000 (GMT) (envelope-from infofarmer@gmail.com) Received: by py-out-1112.google.com with SMTP id c59so357020pyc for ; Wed, 16 Aug 2006 09:31:20 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition:x-google-sender-auth; b=GBBeMPfBYmqJ+nOEhsigMDtm6+Z+rfs7DNVHYcLlvk9Ay5BDGtZSm8+xOUQ6b108ewGVriqG5nSmUt1IqR7H7xIzJHINXau/QM3dShnCVKR+5ET6lW1xrCesMdq072xNkJq0P/9jU5Cskkq582hNuCcjc39/AcWAAfADjgC1PEU= Received: by 10.35.57.5 with SMTP id j5mr1718817pyk; Wed, 16 Aug 2006 09:31:20 -0700 (PDT) Received: by 10.35.105.10 with HTTP; Wed, 16 Aug 2006 09:31:20 -0700 (PDT) Message-ID: Date: Wed, 16 Aug 2006 20:31:20 +0400 From: "Andrew Pantyukhin" Sender: infofarmer@gmail.com To: "FreeBSD Ports" MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Google-Sender-Auth: d8313dfcb64fe232 Cc: Subject: Enforcing "DIST_SUBDIR/DISTFILE" uniqueness X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Aug 2006 16:31:24 -0000 I'd like to propose a policy to enforce a change in DIST_SUBDIR whenever a distfile is rerolled in-place, i.e. when checksum changes, but name stays unchanged. Moreover, effort should be made whenever possible to make the old file available for download from an alternative location. This policy will rid us of some fetch-related headaches. It also will make it possible to share distfiles between hosts with ports trees of different dates. Some rare issues might also be resolved as a result of this. For one, ftp mirrors could be configured to allow upload, but deny modification and/or deletion. One thing I would personally frown upon is using something like "fetch -o othername" to save a file with a different name. It looks all right, but it prevents us from looking for mirrors in an automated way when master sites go down.