porgrc(5)
π porgrc(5) β the glow-up config file π
okay bestie, so porgrc is literally the configuration file for porg. yes, that porg β the source code package organizer, aka porg(8). this page is its manual, and it's giving "system-wide settings" energy. let's get into it π«Ά
β¨ SYNOPSIS β¨
/etc/porgrc
that's it. that's the whole vibe. one path. iconic. π
πΈ DESCRIPTION πΈ
porgrc is the system-wide configuration file for porg(8), the source code package organizer. no cap. that's the job. π
π SYNTAX π
the file is made of two things: comments and key-value pairs. that's the whole menu, girl.
- Comments live on their own separate lines and start with a
#symbol. that's the only way to comment, periodt. - Key-value pairs look exactly like this:
key=value
where key contains no whitespace and no equal signs, and value is all of the text after the equal sign, until (but not including) the ending newline. so yeah, everything up to the line break. π
and here's a lil detail that's lowkey important: the name of key is case insensitive. like, INCLUDE, include and INcludE are all equivalent. same key, different font. slay. β¨
π OPTIONS π
here are all the options you can set. the equivalent command line options (if any exist) are listed in brackets, so you can match them up:
logdir[-L|--logdir] β the baseporglogs directory. default is/var/lib/porg. environment variables like$HOMEare expanded at runtime, so go wild. πinclude[-I|--include] β a colon-separated list of paths to scan when logging the installation of a package. default is/. shell wildcards are allowed in the paths β see PATH MATCHING below for the deets. π¦exclude[-E|--exclude] β a colon-separated list of paths to skip when logging the installation of a package. default is/tmp:/dev:/proc:/sys:/run. shell wildcards are allowed in the paths β again, see PATH MATCHING below. πremove_skip[-e|--skip] β a colon-separated list of paths to skip when removing a package. default is''β which means all logged files are removed. shell wildcards are allowed in the paths, and yes, see PATH MATCHING below. π₯
π PATH MATCHING π
the variables include, exclude and remove_skip all accept a colon-separated list of paths, and each one of those paths may contain shell-like wildcards: *, ? and [..].
files get matched against each of those paths, following the standard shell-like expansion β but with one exception, and it's a big one:
If a path in the list does not contain any wildcard, and it is a directory, it matches any file within that directory.
so no wildcard needed for directories. she just knows. π§
π FILES π
/etc/porgrcβ active configuration file (the one that's actually doing something π )/usr/share/porg/porgrcβ sample configuration file (the inspo board π)
π AUTHOR π
Written by David Ricart (http://porg.sourceforge.net)
π SEE ALSO π
and that's the whole page, bestie!! this was porg 0.10, dated 17 May 2016 β go forth and configure, you absolute main character. mwah πβ¨ππ¦πΈπ«Ά
π¦ where this page comes from
- debian bookworm: porg 2:0.10-1.2 Β· GPL-2.0-or-later
- ubuntu jammy: porg 2:0.10-1.2 Β· GPL-2.0-or-later
- ubuntu noble: porg 2:0.10-1.2build2 Β· GPL-2.0-or-later
- Copyright (C) 2015 David Ricart <http://porg.sourceforge.net>
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms