From owner-freebsd-arch@FreeBSD.ORG Tue Sep 18 21:59:52 2012 Return-Path: Delivered-To: arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 806F81065670 for ; Tue, 18 Sep 2012 21:59:52 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id D1E968FC0C for ; Tue, 18 Sep 2012 21:59:50 +0000 (UTC) Received: by iayy25 with SMTP id y25so374887iay.13 for ; Tue, 18 Sep 2012 14:59:49 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=MPG/xvcYOjFOhx6l1/Gj+uBEi8Gy0rzjkTD8tvOzC6M=; b=ZMFBrl3FWjiw4NVaLB3Lnxv+VhxRHMjsZ3Pwn/vaC8HEKyCFKLPmZisFRAhfpK5BVP 8UF7OuQLqyJ/hDiZanQd8cJPF6t+4FJ5wWjSM0q+yVi2pnGPZjc0IYNTRlBVPidvBaKa zP8BHHGegsZVtSgEw89/oqziOlx11iIw9/XfA+bay6ESKl98ILCtvVbAer3MHXvif2at W57JZhUucnb8TI/VOP6JjVHXvDI61I0xELKBWofZ4F50vzXcJMFHwPsit1BHFc+XyaQT wi3+lt2h+KVFLoL8dRU5aImaTPqSv4DbaB9UbvbmIEnPl7lBAzvVPUrb6XfJ3votLyOW 0UlQ== Received: by 10.50.41.129 with SMTP id f1mr1183519igl.57.1348005589723; Tue, 18 Sep 2012 14:59:49 -0700 (PDT) Received: from 63.imp.bsdimp.com (50-78-194-198-static.hfc.comcastbusiness.net. [50.78.194.198]) by mx.google.com with ESMTPS id cu10sm1347362igc.9.2012.09.18.14.59.46 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 18 Sep 2012 14:59:48 -0700 (PDT) Sender: Warner Losh Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Warner Losh In-Reply-To: <20120918202755.GB26107@ithaqua.etoilebsd.net> Date: Tue, 18 Sep 2012 15:59:45 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: <7AF35799-A94F-4F42-A2D8-7530FD7662CF@bsdimp.com> References: <20120916053523.GJ37286@deviant.kiev.zoral.com.ua> <51B48339-D1FA-49CD-B582-1C58855B024E@bsdimp.com> <50563EA6.1050908@FreeBSD.org> <99E30CDE-AC9D-4615-8830-5EC511EE1BBB@bsdimp.com> <50578D98.7080902@FreeBSD.org> <3649BB84-30A9-4765-8BB6-2484B4B88343@bsdimp.com> <20120918202755.GB26107@ithaqua.etoilebsd.net> To: Baptiste Daroussin X-Mailer: Apple Mail (2.1084) X-Gm-Message-State: ALoCoQlZhUFoUWvYr77cIv5Qdq1mWiL2LdEut1rw0n3Uyfyw6Wgsu/dcNSwRlWXscLWDVErqjCaO Cc: Konstantin Belousov , Eitan Adler , Doug Barton , arch@FreeBSD.org Subject: Re: Fallout from the CVS discussion X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Sep 2012 21:59:52 -0000 On Sep 18, 2012, at 2:27 PM, Baptiste Daroussin wrote: > On Mon, Sep 17, 2012 at 06:03:24PM -0400, Eitan Adler wrote: >> On 17 September 2012 17:52, Warner Losh wrote: >> [snip] >>=20 >>>>>> There is a compromise solution here that I have been hesitant to = offer >>>>>> because I was really hoping that sanity would prevail. But why = not >>>>>> switch the default MK_CVS knob over to "no" now? That will give = us an >>>>>> opportunity to see if there really will be any fallout, and = easily fix >>>>>> it if there is. >>>>>=20 >>>>> I believe that's already been done. >>>>=20 >>>> It isn't now, but it sounds to me like you're saying that you're = not >>>> opposed to doing so? >>>=20 >>> MK_CVS moving to 'no' by default is something we can do right away, = since it is easy to figure out what went wrong for the people using cvs = and putting it back w/o needing to download anything new. Living behind = firewalls can make downloads a pita. I have had systems with very = specific holes that made it a PITA to download anything to them, and it = is a common occurrence. >>>=20 >>>> Eitan, if you're listening, I'd strike while the iron is hot. :) >>>=20 >>> Since I thought that had already been done, please do so. Please = make sure that ObsoleteFiles does the right thing too :) Oh, and make = sure UPDATING is updated. >>=20 >> I have some surrounding commits to get done first. I'd like to get >> some of the existing documentation that refers to CVS removed or >> modified first. >> There is some consensus for making MK_CVS default to "no" early, so >> I'll take that into account and commit that sooner than the above >> listed conditions. >> Does this change require a OSVERSION bump? I'm inclined to say yes = as >> the ports infrastructure might need to be aware of the change. >>=20 > What for? >=20 > I don't see any reason why the ports tree would like to know about the = cvs > removal, do you have something in mind? The following ports define CVS_CMD, or have a naked 'cvs' call in them. japanese/man_doc misc/shuffle net_mgt/rancid net_mgt/rancid-devel sysutils/readlink www/tidy-devel all appear to use the system cvs to check out the sources (except many = rancid, not sure what to make of that). Warner=