rkt logo

Obtaining the INN2.0-beta source tree

Summary of methods of obtaining the INN2.0-beta source tree

1. CVSup, if you can use it, is the best method.
It offers the following significant advantages over other methods:
Disadvantages:
2. httpsync, recently developed by Mib Software, serves a similar purposeto CVSup
but is substantially less complex and easier to compile and install.
Disadvantages of httpsync compared to CVSup.
3. I think the "nightly" tar snapshots at
	    ftp://ftp.isc.org/isc/inn/snapshots
are a less desirable method.


Examine in depth


For a discussion of httpsync and comparison to the other methods (CVSup and tar snapshots.)
see the httpsync home page:
http://www.mibsoftware.com/httpsync/

For instructions on downloading httpsync and using it to synchronize the tree, see:
Using httpsync to get INN2.0-beta

Locations of CVSup are mentioned in a message to inn-workers....
http://www.mibsoftware.com/userkt/inn/dev/inn-workers/vol9709/xfi.htm
And once you have CVSup, you can cut and paste the configuration "supfile" from:
http://www.mibsoftware.com/userkt/inn/dev/inn-workers/vol9709/xdt.htm

Using an AnonCVS mirror is also a possibility.
http://www.mibsoftware.com/userkt/inn/dev/inn-workers/vol9711/xjw.htm


RKT Rapid-Links:[Search] [RKT Tips] Path: / Usenet RKT / For Developers

You are reading from the Usenet RKT
Copyright 1998, Forrest J. Cavalier III, Mib Software
INN customization and consulting
E-mail comments