What does it mean to use ports?

George Hartzell hartzell at alerce.com
Mon Jul 15 03:44:04 UTC 2019

hw writes:
 > Hi,
 > so I wanted to see what would happen if I used a port and removed the
 > emacs-nox packages and its dependencies.  Then I started installing the
 > emacs port.
 > What is going on here?  It seems as if I need to compile the whole
 > system myself now.
 > Is there a way to give all the answers to the questions about compile
 > options at the beginning?  I don't have time to sit around until the
 > next question shows up.
 > What if I want to change the compile options?  How do I make it so that
 > all the packages asking for me for options will do so again?  I don't
 > even remember all the packages that want to be compiled.
 > Can I globally set compile options like -march=native (or whatever the
 > equivalent for FreeBSD is)?

You can also build your own set of packages from the ports (the
official packages are official only because they're built by the
official people...).  There are two different bits of tooling that
automate the process:

- poudriere  -- this is mostly oriented towards building packages
  repos that are used by multiple downstream systems, but I use it to
  maintain the set of packages for my mail server
  - the handbook docs are here:
  - Digital Ocean has a nice tutorial here: https://www.digitalocean.com/community/tutorials/how-to-set-up-a-poudriere-build-system-to-create-packages-for-your-freebsd-servers

- synth  -- mostly oriented towards single system setups, though it
  can easily build shared repos.
  - github repo here: https://github.com/jrmarino/synth


More information about the freebsd-questions mailing list