Date: Mon, 9 Jan 2012 10:19:21 -0800 From: Devin Teske <devin.teske@fisglobal.com> To: "'alexus'" <alexus@gmail.com>, <freebsd-questions@freebsd.org> Subject: RE: ports vs packages Message-ID: <07e401cccefb$364338b0$a2c9aa10$@fisglobal.com> In-Reply-To: <CAJxePN%2BWrr6K83RGFGERzJGUXc24i95BemPOgxqAJW_2Lsfjpg@mail.gmail.com> References: <CAJxePN%2BWrr6K83RGFGERzJGUXc24i95BemPOgxqAJW_2Lsfjpg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> -----Original Message----- > From: owner-freebsd-questions@freebsd.org [mailto:owner-freebsd- > questions@freebsd.org] On Behalf Of alexus > Sent: Monday, January 09, 2012 9:18 AM > To: freebsd-questions@freebsd.org > Subject: ports vs packages >=20 > Ports vs Packages? >=20 > /usr/ports vs pkg_* >=20 > pros/cons >=20 For a very serious production environment, here's our recipe... 1. Always and forever packages first 2. If you can't find it in the pre-compiled packages for your release... th= en use ports 3. But if the port wants too many dependencies, ... we build our own packag= e. Your mileage may vary, but the reason we've adopted this scheme is because = precompiled binary packages already have their dependencies set in stone. O= pposed to ports, if you pull two related packages from the ports-tree at tw= o different times (months apart), then the dependencies may have "floated" = away from your release and therefore, you may end up installing 30+ package= dependencies when it may not absolutely be necessary to do so. We've been doing things this way since FreeBSD 2.2.2-RELEASE (migrated from= 2.2.2 to 4.4, then 4.8, then 4.11, then stuck on 4.11 for some years, and = now 8.1). Of course, this is explicit to rather serious production environments. Desk= top and casual usage ... ports may serve you better if you like to stay up-= to-date rather than only upgrading once every 1-2 years. --=20 Devin _____________ The information contained in this message is proprietary and/or confidentia= l. If you are not the intended recipient, please: (i) delete the message an= d all copies; (ii) do not disclose, distribute or use the message in any ma= nner; and (iii) notify the sender immediately. In addition, please be aware= that any message addressed to our domain is subject to archiving and revie= w by persons other than the intended recipient. Thank you.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?07e401cccefb$364338b0$a2c9aa10$>