Date: Mon, 7 Apr 1997 18:26:23 +0930 (CST) From: Michael Smith <msmith@atrad.adelaide.edu.au> To: avalon@coombs.anu.edu.au (Darren Reed) Cc: msmith@atrad.adelaide.edu.au, hackers@freebsd.org Subject: Re: on the subject of changes to -RELEASEs... Message-ID: <199704070856.SAA06608@genesis.atrad.adelaide.edu.au> In-Reply-To: <199704070819.RAA06256@genesis.atrad.adelaide.edu.au> from Darren Reed at "Apr 7, 97 06:13:58 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
Darren Reed stands accused of saying: > > > Yeah, right. Don't get me started there 8) Just to observe that > > having a set of diffs against "something" is nothing compared to > > having a local copy of the entire CVS repository for the subsystem in > > question. > > What if I don't want an entire CVS repository ? You can either track a given strain with CTM or a given tag with CVSup, or you can just grab the parts of the tree that you are interested in with CVSup. > > And configuring CVSup is _simple_ and _painless_ and it is the > > greatest joy of any software I have ever met in regard to source > > tracking. > > Why do I need CVSup ? What if I don't want to allow CVS through my > firewall (or sup for that matter) ? (at this point, CVSup implies > maintaining a CVS tree as well as a src tree to compile from). You need CVSup because it is the closest thing there is to a reliable, fault tolerant source distribution system. If CVSup is happy that your tree matches that on the server, you can be pretty darn sure it does, unlike things like sup. CTM is good on precision, but can be unhappy if you break something locally. If you are determined to hide behind a firewall, you can either use CTM which delivers to you via mail (and if you weren't accepting that you wouldn't be listening to me 8) or you can use CVSup and SOCKS like I do here. Note that CVSup does _not_ require you to have a local CVS repository, you can use it in checkout mode and just track a given tag, or you can mix and match (use checkout mode for most of the system, but keep a partial CVS repo for the kernel, eg.) > Sure, CVS might be superior to using diffs, BUT, big BUT here, using CVS > will require TWICE the space to store the source. Sure, stuff takes space. That kinda goes with any large object though, and at about 10MB/cent at the moment, space _is_ fairly cheap. > Maybe I bought FreeBSD 2.2 on CD-ROM, I want to upgrade to 2.2.1. > Alternatives currently are: > * buy the new CD when it becomes available > * download all the binaries > * download all the source > * setup cvsup * download Danny's 2.2.1 binary upgrade. * fetch the CTM deltas from the 2.2 baseline to whatever level you want. Note that setting CVSup up in checkout mode and having it update the 2.2 sources to 2.2.1 is actually pretty darn painless. Also note that it's 2.2.1 on the CD, not 2.2. > IMHP, this is not exactly "user friendly". I don't actually see how things could be _more_ "user friendly" unless you had free telephone support. Which I have already offered. > Darren -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199704070856.SAA06608>