Verbosity when logging to /var/log/messages (and printing to screen)

[grahamperrin]

Label: thinking

Origins

A simple example:

% grep 10235 /var/log/messages
Dec 12 07:56:49 mowa219-gjp4-8570p-freebsd pkg[10235]: php81-curl-8.1.13 installed
Dec 12 07:56:49 mowa219-gjp4-8570p-freebsd pkg[10235]: php81-zlib-8.1.13 installed
Dec 12 07:56:49 mowa219-gjp4-8570p-freebsd pkg[10235]: php81-mbstring-8.1.13 installed
Dec 12 07:56:53 mowa219-gjp4-8570p-freebsd pkg[10235]: arcanist-lib-php81-20220518_1 installed
Dec 12 07:57:04 mowa219-gjp4-8570p-freebsd pkg[10235]: glib reinstalled: 2.74.3,2 -> 2.74.3,2 
% pkg query %o glib
devel/glib20
% 

• simple enough, in that prior to use of pkg-upgrade(8) I might have half-memorised the origin of glib

– the subsequent query was, debatably, superfluous.

Use case (a more concrete example)

When reviewing and/or sharing content such as https://pastebin.com/raw/Bt4LdPKN (an extract from /var/log/messages, sorted alphabetically) and https://pastebin.com/raw/AiAArekm:

• it would be useful to have visible origins

– instead, I used my memory to recall graphics/-related packages.

Thinking

At least in the context of the messages file, I can't imagine the additional line length being troublesome.

---

See also:

• 935

[bapt]

The origin is a technical detail of the ports tree, while pkg, do support it for convenience, it should remain a technical detail, the package name is what should matter.

[grahamperrin]

OK, thanks, shall we close this issue?