Date: Tue, 6 Aug 2013 09:50:07 -0400 From: Glen Barber <gjb@FreeBSD.org> To: Thomas Laus <lausts@acm.org> Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD-Update + Sendmail Message-ID: <20130806135007.GA2190@glenbarber.us> In-Reply-To: <5200FE0E.8506.5CB69E@lausts.acm.org> References: <5200FE0E.8506.5CB69E@lausts.acm.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--azLHFNyN32YCQGCU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Aug 06, 2013 at 09:45:50AM -0400, Thomas Laus wrote: > I have been updating my FreeBSD systems for many years by updating and=20 > building from source. For the FreeBSD 9.2 cycle, I decided to use=20 > freebsd-update for binary update instead. I use Sendmail + Cyrus-SASL an= d=20 > the freebsd-update process only installed a 'bare bones' binary. How do = I=20 > compile just Sendmail from source so that it uses my /etc/make.conf for t= he=20 > smtp_auth components? Is there a freebsd-update.conf flag to perform thi= s=20 > task? >=20 No. When you use freebsd-update(8), you get the binary bits that are available on the release images. There is no way to have freebsd-update(8) know of local changes/patches/etc. Glen --azLHFNyN32YCQGCU Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (FreeBSD) iQEcBAEBCAAGBQJSAP8PAAoJEFJPDDeguUajIpEIAJs52Zm4mzB4yrQQVCQHsq8+ AHzXRTfgJ85DXBWzZk18eK2rypYm+hFiB5IpgslDSN4FdWeysmGncNMGU7GU3H6n sH54R2XvbdLeiq/pOrf0LsRI0uSfreZPPBEFkT/EGZpOe07pnmnj3CmgP1zozg+Q ZonNwZoc2dG+buRCCSTf4ldd4+G4hSxcfDt6cheS/Iy6rfwzeA2R6uHZNPpsO6zT KC9LFWWWDaNm9L1D4fyxbH47DliOlZdQUjJoHHM1+4u0tVHih8699QPzdoQu6Ehk dJPqX7BnQ5hVYzAT1giWLnkkPkvshwQsJaH/h7P4XdGniR92ZU7AESlaaj0DbJs= =i7ZG -----END PGP SIGNATURE----- --azLHFNyN32YCQGCU--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130806135007.GA2190>