From owner-freebsd-arch@FreeBSD.ORG Sun Sep 16 20:53:54 2012 Return-Path: Delivered-To: arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 63554106564A; Sun, 16 Sep 2012 20:53:54 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 2753B8FC0A; Sun, 16 Sep 2012 20:53:53 +0000 (UTC) Received: by pbbrp2 with SMTP id rp2so8766851pbb.13 for ; Sun, 16 Sep 2012 13:53:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=8RK/Oau7PgqXk0+bVrT1A2EjsmFydSOTVXQmWEZM/vg=; b=oj4PaQvw2tx+IdtKKuuafULLhI9c35vlRzWOWHjKOpWqDGGBskZc/fc+x0B8fVqKI8 k5DJDbp0g+M9+FjL/JF7SXUWG3c5cKf6l+zB9zefZa81mJiACdLtHKNPNkjtyuIpyL9R mnqr8yuJC8WPU9Zyq/InDYiayTVFriFHScb6xcvUlBFfyjP+yVhqvMQ426WlEvxr2irh pArsAQv0EizmxWJNazKhlBrGkLofmUxghYYGhYiECHdmUSm3l1o8i8Pqv6gDL1YUFkfT BgLhB2gHuUro1UTB15dSIg38tXRkPM4RH7ml7uO+26N4cuQuU5uFhyT35rHNbD0dIDNt TjBA== Received: by 10.68.217.202 with SMTP id pa10mr18462583pbc.15.1347828833584; Sun, 16 Sep 2012 13:53:53 -0700 (PDT) Received: from fuji-wireless.local (c-24-19-191-56.hsd1.wa.comcast.net. [24.19.191.56]) by mx.google.com with ESMTPS id pn4sm5642741pbb.50.2012.09.16.13.53.52 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 16 Sep 2012 13:53:52 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v1278) Content-Type: text/plain; charset=us-ascii From: Garrett Cooper In-Reply-To: Date: Sun, 16 Sep 2012 13:53:51 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <68E67617-A497-48FB-9B63-1AAC06BD60DA@gmail.com> References: <20120916053523.GJ37286@deviant.kiev.zoral.com.ua> <51B48339-D1FA-49CD-B582-1C58855B024E@bsdimp.com> To: Eitan Adler X-Mailer: Apple Mail (2.1278) Cc: Konstantin Belousov , arch@freebsd.org, Adrian Chadd 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: Sun, 16 Sep 2012 20:53:54 -0000 On Sep 16, 2012, at 1:07 PM, Eitan Adler wrote: > On 16 September 2012 15:53, Adrian Chadd wrote: >=20 >> * I'd like to first see a roadmap for doing this - eg, "we're adding = a >> NO_CVS option; CVS will become a port, you can migrate to the CVS = port >> with your next build/installworld"; >=20 > We have WITHOUT_CVS . >=20 >> * if you're that way inclined, backport the NO_CVS option (if it >> doesn't exist) to -9; >=20 > Already done. >=20 >> * Ensure all of the stuff that uses CVS is migrated beforehand, and >> publish all of that effort somewhere; >=20 > This is part of my plan. >=20 >> * Make sure you're doing it for reasons that aren't coming across as >> "GPL free! at all costs!" >=20 > This has nothing to do with the reasons I proposed to remove CVS. > Please re-read my original email. The first words were "CVS is > obsolete." > I had *no idea* CVS was GPLed until the thread started (I thought were > using a BSD licensed one). >=20 >> Now, to stir up trouble, I hereby suggest that if you're going to >> remove CVS because it's no longer used for FreeBSD's project stuff, = we >> should obviously import subversion into the base because _it_ is = being >> used for the FreeBSD project stuff. >=20 > Please re-read the original thread. I am removing CVS because it is > obsolete. CVS being used for FreeBSD project was merely a key blocker > to its removal. >=20 >> Think of why you're not doing that >> (likely because it's already a port/package and there's just as much >> inertia to introduce something to the base system as there is = removing >> it and making it a port) and see if that helps refocus your reasons >> for and against doing things. >=20 > I am not proposing introducing subversion into base because I am not > willing to do the work to maintain it. If I were, that would be a > different story (imho, the base should have sufficient software to > download and compile itself). 1. Subversion changes too much to be in base (its release cycle is = shorter than bind). 2. Subversion sometimes breaks between major/minor versions (1.6->1.7 = comes to mind) and is not backwards compatible in many cases (again, 1.6 = -> 1.7 transition). 3. It requires apr (which optionally requires gdbm), BDB 4.x (which is = GPLv2/GPLv3), sqlite3 (which pulls in tcl because of the distfile the = sqlite3 maintainer chooses to use), neon or serf, etc (point is the = dependency list is not short and thus maintainer overhead is = considerably higher). Please leave it in packages/ports. With pkg_install/pkgng, installing = subversion from a package is trivial and that should be the route taken = for developers, as opposed to having a copy in base. Thanks, -Garrett=