Re: Retrieving the "include" directory for Emacs Modules

[Marco Antoniotti <marcoxa@gmail.com>]

Hello and Happy New (Hacking) Year.

apologies if I insist on this issue.

On Sun, Dec 29, 2024 at 6:53 PM <help-gnu-emacs-request@gnu.org> wrote:

> Message: 5
> Date: Sun, 29 Dec 2024 03:03:53 +0200
> From: Björn Bidar <bjorn.bidar@thaodan.de>
> To: Stefan Monnier via Users list for the GNU Emacs text editor
>         <help-gnu-emacs@gnu.org>
> Cc: Stefan Monnier <monnier@iro.umontreal.ca>
> Subject: Re: Retrieving the "include" directory for Emacs Modules
> Message-ID: <8734i7i9l2.fsf@>
> Content-Type: text/plain
>
> Stefan Monnier via Users list for the GNU Emacs text editor
> <help-gnu-emacs@gnu.org> writes:
>
> >> Those under /usr/lib are looked in by the relevant compilers (they are
> >> include directories private to those compilers, hard-coded into them
> >> when they are built).  Those under /usr/share are private to the
> >> relevant packages, and are either examples or test suites (thus AFAIU
> >> unrelated to the issue at hand here).  Those under /usr/src are what I
> >> mentioned: private headers needed to build a package.
> >
> > Indeed, they each have their own reason to exist.  And this is in Debian,
> > i.e. a distribution which is very careful to install things in the one
> > central place where they belong.
>
> I'm on openSUSE which is entirely unrelated same policy. In fact all
> Unixes have such a policy (macOS doesn't count in this context).
>

... and why exactly MacOSX (and Windows) "don't count in this context"?
And what is the "context"?

>
> > Other relevant cases will look very different:
> > Emacs.app, AppImages, Snap packages, etc...
>
> Who are proprietary platforms such as Snap relevant to Emacs? For these
> where a sandbox is involved such as Snap or Flatpak it is not possible
> to interact with external resources without breaking the security of the
> sandbox.
>

> But anyway this is going off-topic.
>
>
How exaclty does having

include-directory

(and the other variables) available, break the sandbox?  Or anything else?

The issue here is accommodating the wider world.

Personal historical note.  I first used Emacs on a Zentih z8000.  The first
GNU Emacs I used was on a Sun 3/60.  I also used it on AIX and, if memory
does not fail me, on a microVAX with VMS (this I may be wrong).

These were (are) all proprietary platforms.  "Unixy" but proprietary.  As
MacOSX.

Do you want people to use Emacs?  Let them have access to it without
imposing needless constraints.

All the best

MA


-- 
Marco Antoniotti
Somewhere over the Rainbow