Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msuinfo!netnews.upenn.edu!dsinc!spool.mu.edu!howland.reston.ans.net!europa.eng.gtefsd.com!MathWorks.Com!news2.near.net!noc.near.net!shore.shore.net!rwwa.com!witr From: witr@rwwa.com (Robert Withrow) Newsgroups: comp.os.386bsd.development Subject: Re: .../ports and ported software. Date: 14 Sep 1994 21:08:35 GMT Organization: North Shore Access/Eco Software, Inc; (info@shore.net) Lines: 24 Distribution: world Message-ID: <357ooj$qsv@shore.shore.net> References: <356v48$8ut@shore.shore.net> <3575v3$nkk@agate.berkeley.edu> Reply-To: witr@rwwa.com NNTP-Posting-Host: rwwa.com In article <3575v3$nkk@agate.berkeley.edu>, jkh@violet.berkeley.edu (Jordan K. Hubbard) writes: |> Rather than making a central repository of diffs, what I did instead was |> to make each port an encapsulation of the procedure required to make |> it run under FreeBSD. Well, I aplaud what is no-doubt a nice piece of configuration control sleight-of-hand, but I wonder if this system can deal with the problems that stimulated this post. Namely, if I have some version related to, but not identical to one of your ``ports'', what help does your port stuff give? For example, if I have version+1 or perhaps an experimental version of the original code what do I do. If I had just plain-old diffs I would at least know what is involved. But then I am probably just gettin old and crusty in my programming old-age... And, what do you send back to the developers of the ported package, if not just plain-old diffs? You *are* sending back the changes, arent you? -- Robert Withrow, Tel: +1 617 598 4480, Fax: +1 617 598 4430 R.W. Withrow Associates, 319 Lynnway, Lynn MA 01901 USA, Net: witr@rwwa.COM