Hacker News Reader

Comment by dscrd | Hacker News Reader

Personally, I couldn't anymore handle the way ports asks for configuration options for every package that has configurable options. I'm spoiled by the "sane defaults" stance of better Linux distros like Arch.

View on HN

    echo BATCH=1 >>/etc/make.conf

No more prompts for options - they should all certainly have sane defaults. If not, it's a good reason to run send-pr.

I've always been a fan of

    make config-recursive && make install clean

which runs `make config` on the package and all dependencies before installing. It's the best of both worlds IMO -- the port will build unattended and you still have a chance up-front to skim the available options for things you need.

Also

  make -DBATCH install clean

in port directory will do unattended build with default settings. It affects current port and all of its dependencies.

Either set BATCH env variable or use portupgrade/portinstall with -c or -C flags. The latter gathers all the dependencies of a given port and let's you configure them up front, and then the compilation and installation goes without any interruptions.

    -c 
    --config
     	 Run "make config-conditional" before everything for all tasks.
    -C 
    --force-config
     	 Run "make config" before everything for all tasks.

http://www.gsp.com/cgi-bin/man.cgi?topic=portupgrade

Reply on news.ycombinator.com