Date: Sun, 21 Jul 2019 11:09:48 -0700 From: George Hartzell <hartzell@alerce.com> To: hw <hw@adminart.net> Cc: Polytropon <freebsd@edvax.de>, George Hartzell <hartzell@alerce.com>, freebsd-questions@freebsd.org Subject: Re: What does it mean to use ports? Message-ID: <23860.43628.637748.236257@alice.local> In-Reply-To: <8736j6iw12.fsf@toy.adminart.net> References: <87o91wqjl5.fsf@toy.adminart.net> <23851.63340.445828.46420@alice.local> <87sgr7joq7.fsf@toy.adminart.net> <20190716003705.eaa7db5f.freebsd@edvax.de> <8736j6iw12.fsf@toy.adminart.net>
next in thread | previous in thread | raw e-mail | index | archive | help
hw writes: > Polytropon <freebsd@edvax.de> writes: > [...] > The most time consuming part would be to learn and to decide about all > the options of all the packages to compile. Doing that for just one > package like emacs might take weeks because there are so many > dependencies. [...] > > At some point in the process, it might not work out at all because I > picked options in contradiction to dependencies. Setting up the tools > might be the smallest problem. All of that is true, but awfully pessimistic. Often things just work. Other times you have to run down one or two chains of x begets y begets z. I think that learning to build your own things is a good exercise, even if you switch back to pre-built packages. g.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?23860.43628.637748.236257>