08:51 <cruxbot> [opt/3.7]: pure-ftpd: updated to version 1.0.52

08:51 <cruxbot> [opt/3.7]: geeqie: updated to version 2.5

11:08 <ppetrov^> what regex should i use in pkgadd.conf to ignore la files in /usr/lib only (not recursively)

11:36 <farkuhar> ppetrov^: Check out rule_applies_to_file as defined in pkgadd.cc, specifically the lines below regcomp(&preg, rule.pattern.c_str(), REG_EXTENDED | REG_NOSUB). That should indicate what kind of regular expressions are recognized.

11:37 <farkuhar> For instance, if character classes are supported, you might try "INSTALL ^usr/lib/[^/]*\.la$ NO"

11:44 <farkuhar> The lack of documentation here is reminding me of Vitaly's August 2016 thread, which illustrated the difference between the (narrow) intent of the tool designers and the (wider) range of solutions that end users will come up with, when the man-pages do not provide clear guidelines on what is supported.

11:47 <farkuhar> But at least in pkgadd.conf, if you try to use an unsupported regex, then you'll hit a runtime error. So the tool itself provides the necessary guidelines, even if there's no man-page pkgadd.conf(5) explicitly indicating the types of regex that are implemented.

12:13 <ppetrov^> farkuhar, your suggestion seems to work as I wanted

12:13 <ppetrov^> thank you

12:14 <ppetrov^> been messing with some ports depending on the old libxml (2.10) and it seems stuff got linked against the new libxml and la files got in the way

12:34 <farkuhar> ppetrov^: no problem. The definitions of REG_EXTENDED and REG_NOSUB appear in /usr/include/regex.h, but you wouldn't know from the pkgadd man-page that those bitmasks are being used when compiling each regex in pkgadd.conf. It would be easy enough to write a man-page for pkgadd.conf, and then the user wouldn't have to dig into the source code to see how the tools work.

12:40 <farkuhar> Or maybe just extend the existing man-page pkgadd(8), to indicate explicitly which bitmasks are used for compiling each regex. A few more examples of extended regular expressions, under the section CONFIGURATION, would be helpful for users facing similar issues as ppetrov^.

13:10 <farkuhar> uwumeowmeownyaa asked on Tuesday whether CRUX was "essentially a BSD kind of Linux". At least one of the values more prevalent among the BSDs than among Linux distros is a care for the offline documentation. BSD man-pages are known for being super-helpful, allowing users to debug their own problems without resorting to a web search.

13:13 <farkuhar> In fact among the BSDs it's considered a bug if the man-pages are out of sync with the program's observed behaviour, and the devs are receptive to bug reports of man-page inaccuracies or omissions. Meanwhile the man-pages of GNU projects get mostly cosmetic fixes these days, e.g. the removal of "non-inclusive language".

13:17 <farkuhar> So in the spirit of helping CRUX live up to its reputation as "essentially a BSD kind of Linux", I opened a Gitea issue https://git.crux.nu/ports/core/issues/5 to address the omissions in pkgmk.conf(5) and Pkgfile(5). Maybe pkgadd(8) deserves its own issue, based on ppetrov^s regex question.

20:35 <cruxbot> [contrib/3.7]: authelia: 4.38.11 -> 4.38.12

20:35 <cruxbot> [contrib/3.7]: hyperkitty: 1.3.11 -> 1.3.12

20:35 <cruxbot> [contrib/3.7]: libraqm: 0.10.1 -> 0.10.2

20:35 <cruxbot> [contrib/3.7]: postorius: 1.3.12 -> 1.3.13

20:35 <cruxbot> [contrib/3.7]: python3-configobj: 5.0.8 -> 5.0.9

20:35 <cruxbot> [contrib/3.7]: python3-django-allauth: 64.2.1 -> 65.0.0

20:35 <cruxbot> [contrib/3.7]: python3-pdm-backend: 2.3.3 -> 2.4.1

20:35 <cruxbot> [contrib/3.7]: python3-yaspin: 3.0.2 -> 3.1.0

20:35 <cruxbot> [contrib/3.7]: python3-zope-proxy: 5.3 -> 6.0

20:35 <cruxbot> [contrib/3.7]: ruff: 0.6.6 -> 0.6.7

20:45 <cruxbot> [contrib/3.7]: git-cliff: 2.5.0 -> 2.6.0

23:40 <cruxbot> [contrib/3.7]: firefox: 130.0 -> 130.0.1