From: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
To: emacs-devel <emacs-devel@gnu.org>
Subject: (unknown)
Date: Mon, 3 Oct 2022 08:30:27 +0200 [thread overview]
Message-ID: <CAO48Bk9ZLnBQ9==ET17NgK_2X16jkQiJOLX1zZMd4neO2p7=Yw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1571 bytes --]
Rob writes:
> Regarding the writes to HOME, etc. I think David covered that fairly
> well -- Debian runs emacs to "do things" (build .elcs, run tests, etc.)
> at package build time, package install time, and during package testing.
> In all of these cases, we're likely to want to avoid side-effects outside
> the build/test dir like writing .elc or .eln files to the current user's
> HOME, whether that's /root/ or /home/*. It sounds like we may be able
> to accomplish that by redirecting everything to a temp dir, which is
> likely fine.
I know this may come late and be redundant, but just my .01 cents of
experience:
I have my own tweaked Debian infra to build emacs29 for Ubuntu and I have
native-compile enabled. All .eln files generated during build from the
emacs (git) source are stored in /usr/lib/emacs-xyz and are never
recompiled when I run emacs.
What actually gets natively compiled to $HOME/.emacs.d/eln-cache is any
package that I download from (m)elpa-xyz as a result of my
HOME/.emacs.d/init.el
I may be doing something wrong, but AFAIK it seems to work and I have the
same functionality on my Ubuntu natively-compiled Emacs and on the macOS
(both running +/- the same snapshot of the emacs master git branch), where
I have no native compilation.
I hope I somehow contributed something ;-)
/PA
--
Fragen sind nicht da um beantwortet zu werden,
Fragen sind da um gestellt zu werden
Georg Kreisler
Headaches with a Juju log:
unit-basic-16: 09:17:36 WARNING juju.worker.uniter.operation we should run
a leader-deposed hook here, but we can't yet
[-- Attachment #2: Type: text/html, Size: 2037 bytes --]
next reply other threads:[~2022-10-03 6:30 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-03 6:30 Pedro Andres Aranda Gutierrez [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-05-21 2:03 (unknown) Tennyson Bardwell
2024-03-13 12:48 (unknown) Eli Zaretskii
2023-11-18 3:13 (unknown) Greg Minshall
2023-11-18 7:05 ` (unknown) Jim Porter
2023-03-13 6:32 (unknown) Pedro Andres Aranda Gutierrez
2023-03-13 6:18 (unknown) Pedro Andres Aranda Gutierrez
2023-02-11 20:24 (unknown) cheyrn via Users list for the GNU Emacs text editor
2022-07-21 11:36 (unknown) Gregory Heytings
2022-07-09 13:53 (unknown) Lorenzo Isella
2022-07-09 15:06 ` (unknown) Óscar Fuentes
2022-05-29 6:06 (unknown) Pedro Andres Aranda Gutierrez
2022-02-17 19:24 (unknown) hput
2022-02-17 20:03 ` (unknown) Stefan Monnier via Users list for the GNU Emacs text editor
2021-12-20 2:29 (unknown) Davin Pearson
2021-08-23 18:37 (unknown) telegraph
2021-08-23 18:36 (unknown) telegraph
2021-07-27 23:54 (unknown) Troy Hinckley
2021-06-06 8:06 (unknown) Sai Karthik
2021-05-07 12:51 (unknown) Eric Skoglund
2021-05-07 14:40 ` (unknown) Bastien
2020-09-06 7:04 (unknown) Ag Ibragimov
2020-03-15 22:42 (unknown) Arne Babenhauserheide
2019-10-18 2:46 (unknown) Justin Barclay
2019-05-02 0:36 (unknown) Budi
2019-05-02 0:40 ` (unknown) Óscar Fuentes
2018-04-09 23:58 (unknown) siraben
2017-08-30 19:33 (unknown) Mark Oteiza
2017-04-07 23:43 Understanding how to specify UTF-8 Will Parsons
2017-04-13 5:09 ` B. T. Raven
2017-04-13 6:37 ` (unknown) Eli Zaretskii
2017-03-19 16:48 (unknown) Paul Pogonyshev
2017-03-19 19:16 ` (unknown) Mark Oteiza
2017-03-19 19:36 ` (unknown) Paul Pogonyshev
2016-12-28 7:15 (unknown) Chris Gregory
2016-12-28 8:58 ` (unknown) Andreas Schwab
2016-09-28 12:26 (unknown) Takesi Ayanokoji
2016-09-29 13:52 ` (unknown) Byung-Hee HWANG (황병희, 黃炳熙)
2016-02-20 15:28 (unknown) Anders Lindgren
2016-02-08 7:54 (unknown) steve
2016-02-08 8:01 ` (unknown) Steve Purcell
2015-08-10 13:59 (unknown) David Kastrup
2015-08-10 14:02 ` (unknown) David Kastrup
2014-11-13 15:21 (unknown) Eli Zaretskii
2014-11-13 15:30 ` (unknown) Lars Magne Ingebrigtsen
2013-07-04 7:50 (unknown) João Távora
2013-07-06 15:22 ` (unknown) Lars Ingebrigtsen
2013-07-06 17:58 ` (unknown) João Távora
2013-07-06 18:01 ` (unknown) Lars Ingebrigtsen
2012-06-29 13:20 (unknown) Eli Zaretskii
2011-09-17 8:02 (unknown) tester12312
2007-04-04 19:09 (unknown) Jost Burkardt
2005-01-16 15:38 (unknown) mayuko_v_v_sutekimax
2003-05-12 7:59 (unknown) Knowledg1
2003-05-12 7:59 (unknown) Knowledg1
2003-05-01 3:08 (unknown) @Traduire
2003-05-01 3:08 (unknown) @Traduire
2003-04-03 22:41 (unknown) Sebastian Tennant
2003-03-14 6:09 (unknown) Waruna Singappuli
2003-02-02 3:30 (unknown) JMT
2002-04-01 2:15 (unknown) ¿ì¹®°ü
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='CAO48Bk9ZLnBQ9==ET17NgK_2X16jkQiJOLX1zZMd4neO2p7=Yw@mail.gmail.com' \
--to=paaguti@gmail.com \
--cc=emacs-devel@gnu.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.