logoalt Hacker News

What the heck is /pkg?

38 points • by GavinAnderegg • yesterday at 5:21 PM • 13 comments • view on HN

Comments

CharlesW • today at 1:54 AM

> "Turns out, this is part of macOS 27.0…"

Part of macOS 26.4, in fact: https://eclecticlight.co/2026/09/19/macos-tahoe-26-4-changed... "The layout of those hasn’t changed in over six years up to and including macOS Tahoe 26.3.1, but has altered in 26.4 and Golden Gate, with the addition of a new firmlinked directory pkg."

Apple doesn't do this stuff lightly. A search of WWDC sessions doesn't mention /pkg specifically, but I'd bet it's related to this: https://developer.apple.com/videos/play/wwdc2026/206/?time=6...

oefrha • today at 12:56 AM

> It’s also not clear what the “pmk” in /etc/paths.d/10-pmk-global refers to.

Maybe package management kit, if we go by recent Apple naming conventions.

torben-friis • today at 1:19 AM

So they might be aiming for their own brew? Or is there some expectation for a different thing altogether?

jmclnx • today at 2:05 AM

As a NetBSD user, I would guess it is for use with pkgsrc. That would be great for mac people if my wild guess is correct.

http://pkgsrc.org/

➕ show 2 replies
Joker_vD • today at 12:34 AM

> I only started looking into this when I noticed an unfamiliar entry starting with /pkg in my PATH. I assumed something had gone awry. Then I saw that there was, indeed, a /pkg directory in the root of my filesystem. [Emphasis mine —JvD]

See, that's your problem: you think of it as your PATH and your filesystem. But it's actually Apple's and Apple's macOS's filesystem and PATH variable. They may allow you to use those to e.g. store your data and operate on it, but mostly it belongs to them, so they arrange it as they see it better fitting them. And of course, they don't really owe you an explanation of their design decisions, especially such non-user facing ones.

May or may not be /s

➕ show 1 reply