From owner-freebsd-ports@FreeBSD.ORG Tue May 6 02:07:03 2003 Return-Path: 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 B52B637B401 for ; Tue, 6 May 2003 02:07:03 -0700 (PDT) Received: from jkh-gw.queasyweasel.com (adsl-64-173-3-158.dsl.sntc01.pacbell.net [64.173.3.158]) by mx1.FreeBSD.org (Postfix) with ESMTP id AC0F443F93 for ; Tue, 6 May 2003 02:07:02 -0700 (PDT) (envelope-from jkh@queasyweasel.com) Received: from queasyweasel.com (jkh@narcissus.queasyweasel.com [64.173.15.99])h4696Z2J027494; Tue, 6 May 2003 02:06:35 -0700 (PDT) (envelope-from jkh@queasyweasel.com) Date: Tue, 6 May 2003 02:07:08 -0700 Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v552) To: Kris Kennaway From: Jordan K Hubbard In-Reply-To: <20030506085257.GA40932@rot13.obsecurity.org> Message-Id: <1D9E21F6-7FA2-11D7-A9A6-000393BB9222@queasyweasel.com> Content-Transfer-Encoding: 7bit X-Mailer: Apple Mail (2.552) cc: ports@freebsd.org Subject: Re: [kris@FreeBSD.org: cvs commit: ports/net/cvsupit Makefile] X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 May 2003 09:07:04 -0000 I'm not sure I agree. It seems far preferable to "ask around" for someone to do this the right way instead. - Jordan On Tuesday, May 6, 2003, at 01:52 AM, Kris Kennaway wrote: > On Tue, May 06, 2003 at 12:59:40AM -0700, Jordan K Hubbard wrote: >> Sorry, I simply haven't fixed it yet since I'm now having a hard time >> deciding, upon further reflection, whether I shouldn't just kill that >> stupid port. cvsupit started life as a crufty quick hack meant to >> fill >> a short-term purpose (get newbies introduced to cvsup at the time) and >> doesn't serve the longer-term purpose of making cvsup easy to use >> throughout FreeBSD's lifetime. >> >> To do that, if it's even desired, will require release engineering >> assistance to spit out customized cvsupfiles which match whichever >> tags >> are currently in vogue, present dynamic menus of available choices, >> etc. In short, if people really want "cvsupit-like" functionality for >> the long-term then they're just going to have to embed it into the >> "process chain" for release engineering somehow and not just rely on >> some crufty port staying in sync. The "keep the crufty port in sync" >> approach has worked for awhil, but it just isn't practical, IMO, to >> continue doing so any longer. That's unless someone else really has a >> strong lust to step forward and take the cvsupit port over for further >> life-support efforts. > > I believe it's still widely used, so if we need to find a new > maintainer then we should ask around. > > Kris > -- Jordan K. Hubbard Engineering Manager, BSD technology group Apple Computer