From owner-freebsd-questions@FreeBSD.ORG Sun Mar 10 17:18:09 2013 Return-Path: Delivered-To: questions@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 695C6509 for ; Sun, 10 Mar 2013 17:18:09 +0000 (UTC) (envelope-from fbsd8@a1poweruser.com) Received: from mail-03.name-services.com (mail-03.name-services.com [69.64.155.195]) by mx1.freebsd.org (Postfix) with ESMTP id 574717CB for ; Sun, 10 Mar 2013 17:18:08 +0000 (UTC) Received: from [10.0.10.1] ([173.88.202.176]) by mail-03.name-services.com with Microsoft SMTPSVC(6.0.3790.4675); Sun, 10 Mar 2013 10:18:09 -0700 Message-ID: <513CC04C.3020403@a1poweruser.com> Date: Sun, 10 Mar 2013 13:18:04 -0400 From: Fbsd8 User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: Giorgos Keramidas Subject: Re: svn & new pkg system References: <513BC4E2.4040708@a1poweruser.com> <87ppz8ceje.fsf@kobe.laptop> <20795.63556.581627.956239@jerusalem.litteratus.org> <20130310150820.GA20819@saturn> In-Reply-To: <20130310150820.GA20819@saturn> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 10 Mar 2013 17:18:09.0876 (UTC) FILETIME=[3CEBC940:01CE1DB3] X-Sender: fbsd8@a1poweruser.com X-Authenticated-Sender: fbsd8@a1poweruser.com X-EchoSenderHash: [fbsd8]-[a1poweruser*com] Cc: Robert Huff , FreeBSD questions X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Mar 2013 17:18:09 -0000 Giorgos Keramidas wrote: > On 2013-03-09 22:04, Robert Huff wrote: >> Giorgos Keramidas writes: >>> > Is svn going to become part of the base system in 9.2-RELEASE? >>> >>> No. >> [good reasons for not including subversion ellided] >> >> On the other hand ... >> >> The traditional - and I believe still canonical - way of updating the >> system is to recompile from source. >> >> I know I am not alone in feeling the system is substantially >> incomplete if it does not come with all the tools necessary to do >> that. >> >> (Not slighting freebsd-update (don't know enough about it to have an >> opinion); just pointing out it has limitations.) > > This has been traditionally true with CVS, which was also a complex > piece of software, but still merged periodically into FreeBSD src. > > I think it's always a small annoyance when things break away from > 'tradition', but on the other hand tradition shouldn't be able to put > a stop to moving along or act as an impediment for doing our 'real' > work. And the real work of the team is to develop FreeBSD, not to > develop a version control system. There's a lot of know-how and > development happening in the main Subversion development process; > a lof of experience that we do not necessarily need to duplicate > in our own team to do what we like best: that is, develop FreeBSD. > > It's understandable that having to install a package to check-out > the sources is a diversion from previous practice, and it may be > somewhat annoying -- like every change is annoying at first. But > the package is not going to go away and it won't stop working, at > least as long as we are using it ourselves to develop the system. > > So other than the difference that now the sources of the VCS used > for development are not part of src/, conceptually there isn't a > lot of difference from before. The previous state of things was: > > FreeBSD developers use CVS to check out the sources, and > develop the system itself. CVS is available [as part of the > base system] to everyone else who wants to grab a copy of > the source tree. > > WHat happens now is quite similar, except for the bracketed text: > > FreeBSD developers use SVN to check out the sources, and > develop the system itself. SVN is available [as part of the > official packages] to everyone else who wants to grab a copy of > the source tree. > > Your thinking is way to narrow. Besides source, svn can also grab a copy to the ports tree or just a single port. This a much quicker and a more flexible approach than using portsnap. No body has made a case for NOT including svn in the base system. If it can be a port there is no reason why it can not be included in the base system. Just because developers us it is no reason to make life difficult of those who are not devolopers and have other uses for it.