Re: Moving files out of PREFIX on macOS

[Greg Troxel <gdt%lexort.com@localhost>]

ivan%ivanpollak.com@localhost writes:

> According to the documentation it is officially recommended to use
> INSTALL/DEINSTALL to handle cases where files should go outside of
> the ${PREFIX}. [1]

I read that as "files really shouldn't be installed outside of $PREFIX
but if you have to here's how", not "it's great to put things outside of
$PREFIX.

> Also im pretty sure that .App's would be the preferred way of building
> and installing packages due to them being integrated with the base
> system.  XQuartz, the project that allows X11 programs to run on macOS
> is a third-party solution.

Some prefer that I'm sure :-) pkgsrc in general attempts to build things
the same way on all systems, which is the other argument.

> .App's also *should* be self-contained and not have any dependencies
> outside of themselfs [7], thus skipping shlib things should not be a big issue.

pkgsrc doctrine is that libraries should not be vendored, so that when
they are security-bug-fixed and packages rebuilt, all packages have the
fix.  This is messy given rust attitudes and similar.  Are you saying
that every upstream that builds an app either has no non-base-os
dependencies (even with PREFER_PKGSRC) or does static linking, or ?

> Both Homebrew and MacPorts just copy over the file if im not completely wrong.
> Homebrew puts some Apps into ~/Applications and ~/Library/Fonts, MacPorts
> creates /Applications/MacPorts for the Applications from the packet manager.
> [2],[3],[4],[5],[6]

Interesting.  I guess as mac-only packaging they can just go the mac way
and discount the rest of the world.

> Also: I am not using and never will any LLM generated
> content for any of my contributions.

Glad to hear it.  Just mentioning it upfront since I am seeing more and
more or it, and the projects that aren't going full-on vibecoding are
increasingly being strict about LLM rejection (e.g. that's happening in
qgis right now).