3 ms·
LOL. "Wrong!" "Wrong again!" "Still wrong!" Fine. I tracked down the relevant official documentation: https://developer.apple.com/library/archive/documenta
by rectang 6y ago
LOL. "Wrong!" "Wrong again!" "Still wrong!"
Fine. I tracked down the relevant official documentation:
https://developer.apple.com/library/archive/documentation/CoreFoundation/Conceptual/CFBundles/AboutBundles/AboutBundles.html https://developer.apple.com/library/archive/documentation/Co...
> • A package is any directory that the Finder presents to the user as if it were a single file.
> • A bundle is a directory with a standardized hierarchical structure that holds executable code and the resources used by that code.
[...]
> The Finder considers a directory to be a package if any of the following conditions are true:
> • The directory has a known filename extension: .app, .bundle, .framework, .plugin, .kext, and so on.
> • The directory has an extension that some other application claims represents a package type; see Document Packages.
> • The directory has its package bit set.
- codetrotter 6y agoAh, you were right and it was actually packages I was thinking of after all. Thank you and sorry.
- rectang 6y agoThanks for the validation, and I learned something useful tonight! I'd discovered accidentally how to traverse those pseudo-directories, both in the terminal and the finder. Now I know what's actually going on!