all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Rob Browning <rlb@defaultvalue.org>
Cc: emacs-devel@gnu.org
Subject: Re: Possibly defaulting native-compile-target-directory to XDG_CACHE_HOME/...
Date: Sat, 17 Dec 2022 14:08:58 +0200	[thread overview]
Message-ID: <83y1r6grl1.fsf@gnu.org> (raw)
In-Reply-To: <871qozyj6i.fsf@trouble.defaultvalue.org> (message from Rob Browning on Fri, 16 Dec 2022 00:08:37 -0600)

> From: Rob Browning <rlb@defaultvalue.org>
> Date: Fri, 16 Dec 2022 00:08:37 -0600
> 
> 
> We're still trying to resolve some native compilation related crashes in
> Debian in the hope that we'll be able to have 28 in the next stable
> release --with-native-compilation.  (Stage one of the freeze begins on
> Jan 12.)
> 
> One remaining issue is that emacs crashes when HOME=/nope in some of our
> test suites and perhapssome other packaging or install-related
> activities.  For example: https://bugs.debian.org/1021842
> 
> (To refresh, Debian policies require packages not to write outside of a
>  few specified locations in certain situations, e.g. package builds, and
>  HOME is not one of the specified locations.)
> 
> I can't recall from previous discussions whether that crash would be
> considered a bug, or whether emacs just requires a writable cache dir
> now (which is fine if so).

The latter, AFAIU.



  reply	other threads:[~2022-12-17 12:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-16  6:08 Possibly defaulting native-compile-target-directory to XDG_CACHE_HOME/ Rob Browning
2022-12-17 12:08 ` Eli Zaretskii [this message]
2022-12-17 17:42   ` Rob Browning
2022-12-17 18:04     ` Eli Zaretskii
2022-12-17 20:37       ` Rob Browning
2022-12-17 20:59         ` Rob Browning
2022-12-18  8:48         ` Eli Zaretskii
2022-12-24 23:03           ` Sean Whitton
2022-12-25  6:44             ` Eli Zaretskii
2022-12-25  9:22               ` Eli Zaretskii
2022-12-17 15:58 ` Stefan Monnier
2022-12-17 17:38   ` Rob Browning

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83y1r6grl1.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rlb@defaultvalue.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.