From owner-cvs-src@FreeBSD.ORG Fri Aug 5 19:37:09 2005 Return-Path: X-Original-To: cvs-src@FreeBSD.org Delivered-To: cvs-src@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E0C0A16A41F; Fri, 5 Aug 2005 19:37:09 +0000 (GMT) (envelope-from gad@FreeBSD.org) Received: from smtp2.server.rpi.edu (smtp2.server.rpi.edu [128.113.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 349A543D5E; Fri, 5 Aug 2005 19:37:08 +0000 (GMT) (envelope-from gad@FreeBSD.org) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp2.server.rpi.edu (8.13.0/8.13.0) with ESMTP id j75Jb6hF019713; Fri, 5 Aug 2005 15:37:06 -0400 Mime-Version: 1.0 Message-Id: In-Reply-To: <21942.1123270246@phk.freebsd.dk> References: <21942.1123270246@phk.freebsd.dk> Date: Fri, 5 Aug 2005 15:37:05 -0400 To: "Poul-Henning Kamp" , John Baldwin From: Garance A Drosehn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-CanItPRO-Stream: default X-RPI-SA-Score: undef - spam-scanning disabled X-Scanned-By: CanIt (www . canit . ca) on 128.113.2.2 Cc: cvs-src@FreeBSD.org, Maxim.Sobolev@portaone.com, cvs-all@FreeBSD.org, src-committers@FreeBSD.org Subject: Re: cvs commit: src/gnu/usr.bin Makefile X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Aug 2005 19:37:10 -0000 At 9:30 PM +0200 8/5/05, Poul-Henning Kamp wrote: >In message <200508051428.19181.jhb@FreeBSD.org>, John Baldwin writes: > >>> >I have an objections. rcs is useful thing for various administrative >>> >tasks as well (i.e. keeping track of config file revisions), therefore >>> >it is not quite a "toolchain" thing. >>> >>> You are free to keep local patches. >> >>You could always change this to NO_RCS instead and just add that to your >>nanobsd config file. Maybe a NO_SCM that turns off both rcs and cvs? > >Ideally we would have NO_FOO for any program FOO, but that would be >totally unmanageable, so the idea has been to use functional >categories rather than per program. > >If this is really a big deal for people I'll make it NO_RCS, but I >think we're discussion paint again now. Make it a functional category called NO_SCM, and have that cover CVS and RCS. I don't think RCS should be treated as if it's *only* there for the toolchain category. And I think we're as entitled to throw a little paint around as you are to declare the bikeshed already-built and imply that no one is allowed to comment on it. -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@FreeBSD.org Rensselaer Polytechnic Institute; Troy, NY; USA