Date: Mon, 15 Jul 2019 06:08:07 +0100 From: Steve O'Hara-Smith <steve@sohara.org> To: freebsd-questions@freebsd.org Subject: Re: What does it mean to use ports? Message-ID: <20190715060807.18d0301d925376ef3d078076@sohara.org> In-Reply-To: <877e8jq5zm.fsf@toy.adminart.net> References: <87o91wqjl5.fsf@toy.adminart.net> <20190715021053.2f82c84c.freebsd@edvax.de> <23851.53207.561626.837532@jerusalem.litteratus.org> <877e8jq5zm.fsf@toy.adminart.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 15 Jul 2019 06:25:17 +0200 hw <hw@adminart.net> wrote: > Thanks for the warning --- Gentoo has something like that, too. > > Wouldn't I want everything to be optimized for the CPU it's running on? It is rarely worth the compile time (ie. the CPU time saving over the lifetime of the system is less than the CPU time to perform the compilation) to optimise to a particular CPU rather than using generic binaries for the CPU family. Of course for some CPUs and some applications there are big wins to be had, but not on average especially when most software is IO bound not CPU bound. I generally only compile a port for one of two reasons, some cannot be shipped as packages for licensing reasons and some are built with different options to the ones I want (CPU optimisation is one I've not needed but YMMV). When I do need to compile a port the first thing I do is make sure my ports tree is up to date then I use make missing to get a list of dependencies that aren't installed and use pkg to install them first so that I am only compiling the one thing I need to compile rather than all the dependencies. Finally I use pkg lock to prevent package updates overwriting my customised version. -- Steve O'Hara-Smith <steve@sohara.org>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190715060807.18d0301d925376ef3d078076>