Date: Thu, 22 May 2003 23:45:04 -0500 From: Dan Nelson <dnelson@allantgroup.com> To: David Banning <david@skytracker.ca> Cc: questions@freebsd.org Subject: Re: ports versus packages Message-ID: <20030523044504.GA64241@dan.emsphone.com> In-Reply-To: <20030523001419.A81785@skytrackercanada.com> References: <20030523001419.A81785@skytrackercanada.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (May 23), David Banning said: > I was talking to a debian Linux guy the other day who preferred > debians' precompiled packages because, as he put it, "you just load > it, and go, and it always works -." Note that a FreeBSD user can do exactly the same thing by choosing to use packages, either by using "pkg_add -r" or "portupgrade -PP". Or a debian user can choose to download and build from source, using "apt-get source". I've done both myself. > What is the benifit for us to compile versus just installing the package? > - and how come we tend to use the pre-compiled packages less than some > of our fellow *nix users? - (at least that's my perception) I like it because it lets me pick my own settings for a particular package. uw-imap, for example, defaults to disallowing plaintext passwords, and you have to recompile to enable it. Or consider the mutt port, which has many optional patches that can be applied. Then there's the case of software that cannot be redistributed in binary format with modifications, like qmail. -- Dan Nelson dnelson@allantgroup.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030523044504.GA64241>