Date: Fri, 10 Apr 2009 20:28:00 -0400 (EDT) From: vogelke+unix@pobox.com (Karl Vogel) To: freebsd-questions@freebsd.org Subject: Re: sorta newb help compiling samba Message-ID: <20090411002800.32DA9BE71@kev.msw.wpafb.af.mil> In-Reply-To: <49DF9E7A.4030300@gmail.com> (message from Adam Vandemore on Fri, 10 Apr 2009 14:31:06 -0500)
next in thread | previous in thread | raw e-mail | index | archive | help
>> On Fri, 10 Apr 2009 14:31:06 -0500, >> Adam Vandemore <amvandemore@gmail.com> said: A> How do you handle major builds that use FBSD specific patches.... A> asterisk for example? Fortunately I haven't had to build asterisk or anything else that large. If I did, I'd probably try building under Solaris first, and when installing under FBSD, I'd examine any patches and put them in by hand. My only experience with a major ports build was attempting to upgrade Firefox; 20 minutes after starting, I was left with a literally unbootable system. I had to yank the drive, give it to a buddy to verify that my files were still present, do a complete installation with a more recent FBSD version on a clean drive, and restore my stuff from the original system. I'm perfectly willing to admit that I botched something in the Firefox upgrade, but I've also run into problems installing anything that remotely depends on perl. I use the same version on all my servers, and I got tired of seeing "unable to find perl-5.8.whatever"; configure scripts test for capability rather than version number to avoid this problem. Some of my servers are not allowed to have any network access, which means no chasing dependencies; I put in a CD with some source and run a build script. -- Karl Vogel I don't speak for the USAF or my company Seen in an East African newspaper: A new swimming pool is rapidly taking shape since the contractors have thrown in the bulk of their workers.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090411002800.32DA9BE71>