Mark Bixby wrote:

 >The way I approach all of my ports goes something like this:
 >
 >1) Port any dependent subsystems first.

Well, my first step would be to take the copy of the software
I downloaded and check it into CVS first. That makes each
subsequent port that much easier. (This assumes that the software
is not available through a public access CVS server. If the
latter is true, then the "only" way to grab the sources would
be through a cvs checkout from the official repository.)

 >So if I were doing sendmail this time around, I would start with 8.11.3,
 >but it might actually turn out to be 8.12.0 by the time I'm finished,
 >assuming the 8.12.0 beta 7 goes GR by then.

Agreed. Grab the official (e.g. completely working stuff first). If you
port a beta version and something doesn't work, you can't be sure if it
was something you did or something wrong in the package.

 > what can be done to port the next release fast?

Use CVS. Trust me on this one (better yet, try it for yourself).

And Jeff Vance wrote:

 > 2) If it is ok with the list, I am planning on making my port of sendmail
 > completely public.  I will ask many "stupid" questions to the list, apply
 > the answers, ask more and eventually get it ported and running.  My
 > motivation is to make a case study of this port so that others will be
 > more willing to try ports of their own.

Let me suggest that you make the entire port process public, starting with
grabbing the sources, building a CVS hierarchy, etc. Maybe we create a
separate mailing list for this process?

Regards,


M.
--
Mark Klein                                 DIS International, Ltd.
http://www.dis.com                         415-892-8400
PGP Public Key Available

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *