Date: Fri, 17 May 1996 06:14:52 -0700 From: "Jordan K. Hubbard" <jkh@time.cdrom.com> To: "Richard Wackerbarth" <rkw@dataplex.net> Cc: "Michael Smith" <msmith@atrad.adelaide.edu.au>, "FreeBSD Hackers" <hackers@FreeBSD.ORG> Subject: Re: Standard Shipping Containers Message-ID: <3216.832338892@time.cdrom.com> In-Reply-To: Your message of "17 May 1996 07:43:41 CDT." <n1379803457.92277@Richard Wackerbarth>
next in thread | previous in thread | raw e-mail | index | archive | help
> [ Various arguments about CTM, CVS and so on elided ]
Here's my perspective on all of this...
There are 3 ways of getting the sources:
1. Extract the srcdist tarball.
2. Sup:
2a. Configure sup file.
2b. Run supfile first time.
3c. Add optional sup entry to crontab.
3. CTM
3a. Unpack initial deltas
3b. Subscribe to appropriate mailing list.
3c. Add optional alias to aliases.
All three of these techniques constitute perfectly reasonable ways of
getting the sources, depending on your needs. Only one of these
techniques is automated enough to make it currently usable a in semi-
automated fashion by sysinstall, however, and that's #1.
If anyone on either side of the great sup vs CTM debate would care to
automate steps a-c for their syncronization mechanism of choice, I'll
be more than happy to help with the actual integration of same into
sysinstall. The installation procedure should, of course, be as
novice-friendly as sysinstall in general (so I'm not setting the goals
all that high :-) and implemented in a manner similar to the
configApache() or configSamba() routines (see /usr/src/release/sysinstall
sources for details).
I personally think that this feature is overdue, but I haven't time to
implement configSUP() and configCTM() myself so I'd really need
someone else to do the coding. Considering the relative paucity of
questions to ask ("What directory do you want to keep your sources
in?"), it should be a fairly easy task.
Jordan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3216.832338892>