From owner-freebsd-chat Fri May 22 11:20:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA12432 for freebsd-chat-outgoing; Fri, 22 May 1998 11:20:36 -0700 (PDT) (envelope-from owner-freebsd-chat@FreeBSD.ORG) Received: from internationalschool.co.uk (root@[194.72.37.214]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA12001 for ; Fri, 22 May 1998 11:19:17 -0700 (PDT) (envelope-from stuart@internationalschool.co.uk) Received: from internationalschool.co.uk (bamboo.tis [10.0.0.70]) by internationalschool.co.uk (8.8.8/8.8.8) with ESMTP id TAA09166; Fri, 22 May 1998 19:15:43 +0100 (BST) Message-ID: <3565C10A.DF047499@internationalschool.co.uk> Date: Fri, 22 May 1998 19:16:42 +0100 From: Stuart Henderson Organization: The International School X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 2.2.6-STABLE i386) MIME-Version: 1.0 To: Tim Vanderhoek CC: bjc23@hermes.cam.ac.uk, chat@FreeBSD.ORG, Malartre Subject: Re: Why installing ports on a computer? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Tim Vanderhoek wrote: > > Whatever is wrong with using CVSup to keep one's ports tree > up-to-date? I wasn't thinking so much of keeping things up to date, rather a way around having /usr/ports extracted to disk except when needed. Unpacking ports.tgz is the slowest part of the installation for most people and it eats a lot of space.. The only (minor) problem I have using cvsup to track the ports tree is that dependencies are installed based on the version number and not the port name - in many cases this is a good thing, but it can result in spending a long time fetching and making new versions of perl5,etc. that often aren't really needed. Stuart To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message