From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Possibly defaulting native-compile-target-directory to XDG_CACHE_HOME/... Date: Sun, 18 Dec 2022 10:48:28 +0200 Message-ID: <83wn6pf677.fsf@gnu.org> References: <871qozyj6i.fsf@trouble.defaultvalue.org> <83y1r6grl1.fsf@gnu.org> <875yeaexk5.fsf@trouble.defaultvalue.org> <838rj5hppe.fsf@gnu.org> <871qoxg41t.fsf@trouble.defaultvalue.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="31952"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Rob Browning Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Dec 18 09:49:23 2022 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1p6pMJ-00085l-3X for ged-emacs-devel@m.gmane-mx.org; Sun, 18 Dec 2022 09:49:23 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1p6pLY-0001Tp-Nq; Sun, 18 Dec 2022 03:48:37 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1p6pLM-0001TF-Hy for emacs-devel@gnu.org; Sun, 18 Dec 2022 03:48:25 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1p6pLL-0006gH-Sn; Sun, 18 Dec 2022 03:48:23 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=JW+uuHH1jtxBFEAZHFvgfk8xw7F5IX5nYx32vaIA4mY=; b=HduxUlw13QJY 8JT8h1EQTpRqCrmZbt8GhyxQTAt+8dJOMwW3nViKsrZByBScnG0dE+PTRYmWxJZOg0EkdkPR0Qamj eiPQ3tP6r6yzoXfFjHz2YSZk/ODcC/dJLC4m8DEAMJX6ckZlBXKFet5IOUvRwFpkxebsGYqKNYa17 9vyvNsA6rugdC8LWnaHM3LYY8r/jv844JB3tiQtI5LqoKcdPHFNmOwejhH800nB1kXv97yyY+xImT vjKKmdLKHZtDjxV8X6bMcHAcrn+WTet8qM02cWmeUnP1KsidQYyd7nUVTz/D0BVzCqzYl9Rh5aydU gFIML96PPUouXpMPQTdidw==; Original-Received: from [87.69.77.57] (helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1p6pLJ-00087V-JA; Sun, 18 Dec 2022 03:48:22 -0500 In-Reply-To: <871qoxg41t.fsf@trouble.defaultvalue.org> (message from Rob Browning on Sat, 17 Dec 2022 14:37:18 -0600) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:301602 Archived-At: > From: Rob Browning > Cc: emacs-devel@gnu.org > Date: Sat, 17 Dec 2022 14:37:18 -0600 > > Eli Zaretskii 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...)? No. I'm saying that these users should add a one-liner to their init file. > ...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? I don't understand this part. What do you mean by "happen early enough"? > 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. Is there something in emacs-buttercup that makes it necessary for reproducing this? Or would any byte-compiled file do? Anyway, what happens if you try this with Emacs 29? Emacs 28 is in the past for us: there will be no more releases from the emacs-28 branch. And on Emacs 29 we made some changes which I think should prevent these problems.