Date: Mon, 1 May 95 20:50:31 MDT From: terry@cs.weber.edu (Terry Lambert) To: julian@freefall.cdrom.com (Julian Elischer) Cc: hackers@freefall.cdrom.com Subject: Re: policy with sources imported.. Message-ID: <9505020250.AA05147@cs.weber.edu> In-Reply-To: <199505020219.TAA15598@freefall.cdrom.com> from "Julian Elischer" at May 1, 95 07:19:52 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> Very often I want to compile something from FreeBSD, for another OS, so that > I have compatible versions. This of course means I have to 'UN-PORT' it. > I understand that for the ports, we have a lead back to the original > versions, but for things that are imported, there are no such links.. > Why do you have to 'UN-PORT' it? Is it the makefile stuff? I thought it would be a nice thing if the makefile stuff could be easily cross-built to allow the packages to mostly "just compile" on other platforms. I did notice a distinct lack of portability for things like tcsh and telnetd, though; I would think it would be a goal to make sure that the code didn't get "deportablized" as it was imported -- I was really suprised at some of the things that wouldn't build for SunOS. Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9505020250.AA05147>