From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Gunnar Horrigmo Newsgroups: gmane.emacs.devel Subject: Re: Add a configure option for NATIVE_FULL_AOT? Date: Fri, 20 Aug 2021 15:06:46 +0200 Message-ID: References: <83bl5w70vw.fsf@gnu.org> <834kbo6xm5.fsf@gnu.org> <87zgtg3x4i.fsf@wavexx.thregr.org> <83zgtg57jv.fsf@gnu.org> <83k0ki36at.fsf@gnu.org> <83czq81jg8.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="33076"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Aug 20 15:07:39 2021 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 1mH4FF-0008Ly-Sp for ged-emacs-devel@m.gmane-mx.org; Fri, 20 Aug 2021 15:07:38 +0200 Original-Received: from localhost ([::1]:41990 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mH4FE-0001Gb-Sg for ged-emacs-devel@m.gmane-mx.org; Fri, 20 Aug 2021 09:07:36 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:49138) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mH4Ef-0000bJ-KI for emacs-devel@gnu.org; Fri, 20 Aug 2021 09:07:01 -0400 Original-Received: from aibo.runbox.com ([91.220.196.211]:55614) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1mH4Ea-0007Hb-9b for emacs-devel@gnu.org; Fri, 20 Aug 2021 09:06:59 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=runbox.no; s=selector2; h=Content-Transfer-Encoding:Content-Type:MIME-Version: Message-ID:In-Reply-To:Date:References:Subject:To:From; bh=KNx8V6ONWWKsxQ3YA67jGZPfcYRmXQf1mJ57oQjaKws=; b=ajX/8HQwDIGotcf3RO8sLenc8n ftqmOSY3nSsskhUDqa+pl5Z+DUU6CFfIop1qIm+3Y9NIIxAx4lTiGkKzE+IFr/GE2y4vNaPGrkhzY D/s3SEP2U4J4o6FyYU1FrlWyD/KXlI6hai/enui05JjSX0iwc+dM6jWidIGN9T1bQnvlIKAof5Qv+ HmkFcAlE8JKu1fxaod5FRdySJixDhCRtY0BDzLV/BKWu1ogjIUom99CQBwU4QCKSXUkmkSqTOaYb8 rs6c3vVTRF7K0ucbV4tTcuf9o0UZ5dfEm9cgxXfjNPKlc7cYakVwrJGpqTAKWeLWI33+rFu1xr4j/ UlwSf7lA==; Original-Received: from [10.9.9.74] (helo=submission03.runbox) by mailtransmit03.runbox with esmtp (Exim 4.86_2) (envelope-from ) id 1mH4EX-0006Xt-68 for emacs-devel@gnu.org; Fri, 20 Aug 2021 15:06:53 +0200 Original-Received: by submission03.runbox with esmtpsa [Authenticated ID (9149)] (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) id 1mH4ER-0007EP-9K for emacs-devel@gnu.org; Fri, 20 Aug 2021 15:06:47 +0200 In-Reply-To: <83czq81jg8.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 20 Aug 2021 13:47:35 +0300") Received-SPF: pass client-ip=91.220.196.211; envelope-from=horrigmo@runbox.no; helo=aibo.runbox.com X-Spam_score_int: -27 X-Spam_score: -2.8 X-Spam_bar: -- X-Spam_report: (-2.8 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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" Xref: news.gmane.io gmane.emacs.devel:272721 Archived-At: Eli Zaretskii writes: >> From: Gunnar Horrigmo >> Eli Zaretskii writes: >> > >> > AFAIR, the main argument against using the XDG's cache was that the >> > definition of its purpose didn't fit, and that XDG directories are >> > ephemeral. >>=20 >> I don't know why that is a problem, but if it is, then the right place >> would be $XDG_STATE_HOME or $XDG_DATA_HOME? I think?=20 > > What is the definition of "state files" and "data files" for this > purpose? Just be considering the usual meaning of these, *.eln files > are neither, but maybe the Freedesktop definitions are not "usual". | $XDG_DATA_HOME defines the base directory relative to which | user-specific data files should be stored. If $XDG_DATA_HOME is either | not set or empty, a default equal to $HOME/.local/share should be | used. |=20 | $XDG_STATE_HOME defines the base directory relative to which | user-specific state files should be stored. If $XDG_STATE_HOME is | either not set or empty, a default equal to $HOME/.local/state should | be used. |=20 | The $XDG_STATE_HOME contains state data that should persist between | (application) restarts, but that is not important or portable enough | to the user that it should be stored in $XDG_DATA_HOME. It may | contain: |=20 | actions history (logs, history, recently used files, =E2=80=A6) |=20 | current state of the application that can be reused on a restart | (view, layout, open files, undo history, =E2=80=A6) So I guess you're right about XDG_STATE_HOME. But I think we should be=20 free to define what data is ourselves? There is also this, just for completeness sake: | $XDG_RUNTIME_DIR defines the base directory relative to which | user-specific non-essential runtime files and other file objects | (such as sockets, named pipes, ...) should be stored. The directory | MUST be owned by the user, and he MUST be the only one having read | and write access to it. Its Unix access mode MUST be 0700. | | The lifetime of the directory MUST be bound to the user being logged | in. It MUST be created when the user first logs in and if the user | fully logs out the directory MUST be removed. If the user logs in more | than once he should get pointed to the same directory, and it is | mandatory that the directory continues to exist from his first login | to his last logout on the system, and not removed in between. Files in | the directory MUST not survive reboot or a full logout/login cycle. | | The directory MUST be on a local file system and not shared with any | other system. The directory MUST by fully-featured by the standards of | the operating system. More specifically, on Unix-like operating | systems AF_UNIX sockets, symbolic links, hard links, proper | permissions, file locking, sparse files, memory mapping, file change | notifications, a reliable hard link count must be supported, and no | restrictions on the file name character set should be imposed. Files | in this directory MAY be subjected to periodic clean-up. To ensure | that your files are not removed, they should have their access time | timestamp modified at least once every 6 hours of monotonic time or | the 'sticky' bit should be set on the file. That said, I really didn't mean to challenge already made decisions. Especially in the runup to 28. I'm perfectly happy to live with the current situation. >> >> I won't attempt to revive that discussion, but is there some guidance= on >> >> how to configure this in .emacs (probably not, but by any means), so = we >> >> can have a more... compliant environment (if you'll excuse the term)? >> > >> > I don't think I have a clear understanding of what you want to >> > achieve, so please tell more. >>=20 >> I simply want to store the .eln files in an XDG defined directory, even >> if you guys think I shouldn't. :) > > You can always customize native-comp-eln-load-path, can't you? I can indeed. I guess this is what I originally meant to ask. Thank you for the pointer, and sorry for the disruption. I should have investigated instead of letting my OCD panic. :) --=20 Gunnar