From owner-freebsd-libh Thu Oct 26 5:37: 2 2000 Delivered-To: freebsd-libh@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id AF91437B4CF for ; Thu, 26 Oct 2000 05:36:48 -0700 (PDT) Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id e9QCaY449572; Thu, 26 Oct 2000 05:36:39 -0700 (PDT) (envelope-from jkh@winston.osd.bsdi.com) To: kientzle@acm.org Cc: libh@freebsd.org Subject: Re: BOF at BSDCon: FreeBSD Installer, Packages System In-Reply-To: Message from Tim Kientzle of "Mon, 23 Oct 2000 16:17:11 PDT." <39F4C6F7.679F562D@acm.org> Date: Thu, 26 Oct 2000 05:36:34 -0700 Message-ID: <49568.972563794@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-libh@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Yes, but CD-ROMs are still only 650MB. Are you willing to cut maybe 25% > of the packages out of the CD-ROM distro? (I've seen many cases > where ZIP files are nearly double the size of .tar.gz files. Have you > compared ZIP and tar.gz versions of the ports collection?) And there > are still a lot of people running over 28.8kbps modems; historically, > bandwidth grows a lot more slowly than hard disk space. Hmmm. I guess I'm not really sure yet; it's not an insignificant point you raise there, the jury is simply still out on how serious it would be in practice. > As for selective install, I'm very confused. Any streamable archive > format will allow you to choose on-the-fly whether or not to write > the next file to disk. If you have the manifest information up front, > then you can decide on a file-by-file basis. If you're assuming that > the archive is always available on a local disk (which is a requisite > for single-file random access). I'm not assuming it's always available, but it will be available in a large number of cases since a lot of people install from CDROM or NFS as well as FTP. > Huh? You have to _compile_ a program to run in /usr/local; why not > just _compile_ it to run in /usr/package/xxxx/? E.g., for any > program that uses GNU autoconf (which definitely includes emacs): The issue is that you're NOT compiling it when you install it as a package, and that's the point where many people would like to change the prefix. What if I don't like /usr/package but prefer /pkg? Or what if I still like /usr/local? Saying "well, you gotta build it from the port then" is to miss the whole point of ports/packages transparency and trying to make them essentially equivalent as far as the end result is concerned. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-libh" in the body of the message