Re: Possibly defaulting native-compile-target-directory to XDG_CACHE_HOME/...

[Rob Browning]

Eli Zaretskii <eliz@gnu.org> writes:

> I don't see how this follows from what I said.  There should be a
> writable directory, but it doesn't have to be under HOME.  You can
> change the value of native-comp-eln-load-path to have there any
> directories you like.  We've been through this during the previous
> discussion, I believe.

I may not have understood where all of that ended up.

Given that there's no way to establish the location via an envt var.
Are you saying that anyone who needs to run emacs with an unwritable
home would need to add one or more command line arguments to every
invocation (i.e. we'd need to do that across all of the relevant debian
testing scripts, etc., some of which may be embedded in upstream
frameworks -- I guess we might also just shadow emacs in the path with a
wrapper script...)?

...and if any of the relevant command line settings don't happen early
enough, then that'd be considered a bug that we'd want to report and see
about fixing?

Oh, and I can finally reproduce that buttercup crash with an upstream
tree.  This should do it:

  # Build and install emacs-28.2 as root or "user1"

  # As "user2" (not root or user1)
  git clone https://github.com/jorgenschaefer/emacs-buttercup.git
  cd emacs-buttercup
  export HOME=/nope
  rm -f *.elc
  emacs -Q -batch -L . -f batch-byte-compile buttercup.el buttercup-compat.el
  emacs -Q -batch -L . -l buttercup -f buttercup-run-discover

The key appears to be that the install must be as some other user.

Thanks
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4