From owner-freebsd-ports Sun Sep 28 23:19:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA20721 for ports-outgoing; Sun, 28 Sep 1997 23:19:14 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA20703 for ; Sun, 28 Sep 1997 23:19:11 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id XAA08908; Sun, 28 Sep 1997 23:19:01 -0700 (PDT) To: jgrosch@superior.mooseriver.com cc: ports@FreeBSD.ORG Subject: Re: Uh oh.. Time to take another look at the packages collection! In-reply-to: Your message of "Sun, 28 Sep 1997 23:12:59 PDT." <19970928231259.30273@mooseriver.com> Date: Sun, 28 Sep 1997 23:19:01 -0700 Message-ID: <8904.875513941@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-ports@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Why not split the packages into several groups roughly as follows; Perhaps I should clarify my earlier message: I'm not seeking where to draw the lines, I'm seeking *how* to draw the lines. It's all well and good to say "split 'em into ports with the letter 'r' in their names and ones without" but that still leaves the question open as to how we're going to automate this and what the end-user impact is going to be. Let's say I'm installing with my media type set to FTP, and my site has plenty of space and a single packages/INDEX file. That's the simple case, but what about when the packages are split across 2 CDs? Is each package collection stand-alone or do we implement some sort of "TOC" mechanism that lets INDEX file entries point elsewhere? Neither of the above? Jordan