From owner-freebsd-ports Tue Mar 11 07:59:33 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id HAA14517 for ports-outgoing; Tue, 11 Mar 1997 07:59:33 -0800 (PST) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA14497; Tue, 11 Mar 1997 07:59:27 -0800 (PST) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id HAA09750; Tue, 11 Mar 1997 07:59:32 -0800 (PST) To: Eivind Eklund cc: ports@freebsd.org, current@freebsd.org Subject: Re: Getting /usr/ports everywhere... In-reply-to: Your message of "Fri, 07 Mar 1997 14:23:27 +0100." <3.0.32.19970307142325.00ce8210@dimaga.com> Date: Tue, 11 Mar 1997 07:59:30 -0800 Message-ID: <9736.858095970@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-ports@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > CTM/sup/CVSup is one of the things that really set FreeBSD apart. It would > be a Good Thing to make it more accessible; I at least want as many people > as possible to run it, as they'll never go back to anything less than daily > upgrades :) Well, for this I've always envisioned something a little bit different in the standard Distributions menu for the future. Say you select "source" and that brings you to a submenu saying: [ ] I want the CVS repository, with all source information. [ ] I want just the sources for this version of FreeBSD. [ ] I want to unpack a static source tree from the distribution. [ ] I want a constant "live feed" for this source tree via CTM. [ ] I would prefer to update it at will with CVSup. And depending on what you choose, you get tossed into another area of Q&A about where you want to receive the CTM updates or where the CVSup files should go, etc and so forth, and it's all automated. Once the user has chosen which "source program" to apply for, the updates just happen automagically from then on out. That's the way I'd like it to be, anyhow, but unfortunately all of that also takes time and work, too... Heck, it took me over two years just to get a registration screen into sysinstall. I don't see an immediate opportunity for adding easy automated source tracking. :-) Jordan P.S. That's also my sneaky way of saying that if anyone else had a penchant for hacking this sort of thing into sysinstall, I'd be more than happy to point them in the right directions. :)