From owner-freebsd-chat Fri May 22 17:46:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA29936 for freebsd-chat-outgoing; Fri, 22 May 1998 17:46:41 -0700 (PDT) (envelope-from owner-freebsd-chat@FreeBSD.ORG) Received: from hwcn.org (ac199@james.hwcn.org [199.212.94.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA29885 for ; Fri, 22 May 1998 17:46:07 -0700 (PDT) (envelope-from hoek@hwcn.org) Received: from localhost (ac199@localhost) by hwcn.org (8.8.8/8.8.8) with SMTP id UAA23548; Fri, 22 May 1998 20:39:53 -0400 (EDT) Date: Fri, 22 May 1998 20:39:53 -0400 (EDT) From: Tim Vanderhoek To: Stuart Henderson cc: Tim Vanderhoek , bjc23@hermes.cam.ac.uk, chat@FreeBSD.ORG, Malartre Subject: Re: Why installing ports on a computer? In-Reply-To: <3565C10A.DF047499@internationalschool.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 22 May 1998, Stuart Henderson wrote: > 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.. If it really is too large, maybe it is time to break off the ja-, ko-, etc. lang-specific ports into a separate installation packet. It seems to me, though, that installation is a one-time thing and the amount of time it takes to unpack ports.tgz doesn't really figure when you view it that way... > 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. Don't expect this to get fixed anytime soon. It would require significant manpower to say what things really are needed, and what old versions will suffice. We have nowhere near the manpower resources to handle the increase in support and debugging that would be generated, IMO. You're going to have that problem regardless of how you track the ports tree. It is not specific to using CVSup. -- Outnumbered? Maybe. Outspoken? Never! tIM...HOEk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message