From: Ken Brown <kbrown@cornell.edu>
To: cygwin <cygwin@cygwin.com>
Subject: autorebase and user-installed dynamic objects
Date: Sat, 18 Sep 2021 18:51:31 -0400 [thread overview]
Message-ID: <4f799e88-40cd-2cdc-6d40-0285e66f5be0@cornell.edu> (raw)
Achim,
In preparation for using emacs's new native compilation feature, I've been
experimenting with using autorebase to rebase the *.eln files created in a
user's home directory. As a start, I created a file
/var/lib/rebase/user.d/kbrown
containing the line
/home/kbrown/.emacs.d/eln-cache .
I also modified /usr/bin/rebaseall and /usr/bin/rebaselst so that they would
recognize 'eln' as a suffix of a file needing to be rebased. I then ran setup
and let it do its autorebase, but the *.eln files didn't get rebased.
Looking into /usr/bin/rebaselst, I think I see the problem. The function
rebase_user() greps the file /var/lib/rebase/user.d/kbrown for the relevant
suffixes, instead of looking for files in /home/kbrown/.emacs.d/eln-cache.
Shouldn't rebase_user use a variable "userLocs" analogous to the variable
"dynLocs" used by rebase_dyn()? Or am I completely misunderstanding how this is
supposed to work?
Thanks.
Ken
next reply other threads:[~2021-09-18 22:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-18 22:51 Ken Brown [this message]
2021-09-19 6:18 ` ASSI
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=4f799e88-40cd-2cdc-6d40-0285e66f5be0@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin@cygwin.com \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).