PORTSLOGGER(1)

πŸ“¦ in nixpkgs unstable

πŸ’… PORTSLOGGER(1) πŸ’…

🌸 NAME 🌸

portslogger β€” logs ports builds selectively, and yes bestie this lil page is from the General Commands Manual πŸ’–

✨ SYNOPSIS ✨

portslogger [-s] directory

πŸŽ€ DESCRIPTION πŸŽ€

Okay so portslogger saves logs from ports build in separate files. Very organized, very demure, very cutesy πŸ’…

It handles directory change messages from the ports tree infrastructure and switches to a corresponding log file situated in directory accordingly. Like, e.g., it will log the build from screen in directory/screen-4.0.3p1.log β€” literally slay.

portslogger will filter progress-bar noise from ftp(1), pkg_add(1), and pkg_create(1). No cap, it's giving clean logs only ✨

By default, portslogger acts as a filter and still passes its input to stdout, unless run with -s. That's the whole flag situation from the synopsis, bestie β€” -s is right there in portslogger [-s] directory.

It is most often used as

$ make package 2>&1 | portslogger logdir

or in conjunction with tmux(1), such as

$ tmux pipe-pane 'portslogger -s logdir'
πŸ¦‹ so iconic: pipe your build into it, or let tmux(1) pipe-pane it for you. Either way, the logs are getting their own little homes.

πŸ”₯ SEE ALSO πŸ”₯


source/version: Debian Β· date: June 26, 2018 β€” okay bye bestie, that's the whole page πŸ«ΆπŸ’œ

πŸ“¦ where this page comes from
  • nixpkgs unstable: cvs-export
  • πŸ’– girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms