Date: Thu, 12 Sep 2024 11:48:02 -0700 From: Pete Wright <pete@nomadlogic.org> To: questions@freebsd.org Subject: Re: port installation basics Message-ID: <21907abe-cd05-475e-9592-b83307fae2e2@nomadlogic.org> In-Reply-To: <qZcAapFiQBQtJ9P1@aceecat.org> References: <qZcAapFiQBQtJ9P1@aceecat.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 9/12/24 11:25, fatty.merchandise677@aceecat.org wrote: > Hello, I'm trying FreeBSD again (penguin news is depressing) and I > face again some of the problems I remember. welcome! > I am torn between packages and ports. I read discouraging things about > using both, and yet I seem to need both for the following reasons: I would recommend starting with packages, it will certainly save you a lot of time and effort to getting a running system. Heck, once you have a list of packages you need it makes it pretty trivial to just re-image systems if you want a fresh start while learning how things work. Having said that, I think it's pretty common to have systems with a mixture of default upstream packages in addition to ones you build locally. For example, I have a few patches I like for some port called "www/some-server". What I do is go into the "www/some-server" directory in the ports tree then run "make package". Then I can use the pkg utility to install this locally built software with my patches. This keeps everything consistent in terms of 3rd party software all being managed by the pkg utility. I'd also keep a copy of the FreeBSD handbook handy while you hack on this - it's pretty dang good. One tool you may want to explore once you get your footing is Poudriere. It's very useful for bulk package building, or building cross-release software: https://docs.freebsd.org/en/books/handbook/ports/#ports-poudriere -pete -- Pete Wright pete@nomadlogic.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?21907abe-cd05-475e-9592-b83307fae2e2>