On Thu 04 Dec 04:34, Dan Mahoney (ports) wrote: > > > > On Dec 4, 2025, at 2:50 AM, Baptiste Daroussin <[email protected]> wrote: > > > > On Thu 04 Dec 11:03, Baptiste Daroussin wrote: > >> On Thu 04 Dec 01:23, Dan Mahoney (ports) wrote: > >>> All, > >>> > >>> We've been using puppet on many of our systems to manage installed ports, > >>> and we've always defaulted to telling pkg to install the lowercase name > >>> of a package. > >>> > >>> Recenty, we're noticing that pkg fails to install p5-ipc-run3, and that a > >>> pkg search won't find it anymore because it's in the tree as p5-IPC-Run3. > >>> > >>> Did pkg recently change to be case-sensitive? > >>> > >> > >> The fact that pkg was case sensitive was a bug, which has been harmless > >> for a > >> while, until people started playing with packages named "FreeBSD-" vs > >> packages > >> named "freebsd-" with the same suffix. > >> > >> Note I just figured a bug which makes the pkg.conf setting which > >> determines this > >> behaviour bugging and not working consistently everywhere (well actually > >> working > >> in most cases). I am fixing this part right now. > >> > >> Best regards, > >> Bapt > > > > Side note: if you want a consistent and predictible behaviour the -C/-i > > options > > are still working the same for all versions of pkg. > > That would require rewriting puppet's package provider. It's easier to > update our manifests now that we know this is a thing, and I'm sure there > will be Gotchas, especially with the CamelCase perl ports. > > Thanks for the quick answer.
To be honnest in the package world where case matters, it is kind of weird to rely on case sensitivity in automation tools. (never the less you should not have been taken by surprise, my apologies for this). That said, now (in git) pkg is fixed and properly respect everywhere what ever the user will have defined in their pkg.conf for the value CASE_SENSITIVE_MATCH (defaulting to yes) I have a couple of PR to review and will issue a pkg 2.5.0 release. Best regards, Bapt
