From: Ken Brown <kbrown@cornell.edu>
To: cygwin-apps@cygwin.com
Subject: Re: autorebase and user-installed dynamic objects
Date: Mon, 20 Sep 2021 08:57:22 -0400 [thread overview]
Message-ID: <51a8043a-a8cb-840f-866e-53d64aac1ebe@cornell.edu> (raw)
In-Reply-To: <87ilyv94a0.fsf@Otto.invalid>
On 9/20/2021 1:58 AM, ASSI wrote:
> Ken Brown via Cygwin-apps writes:
>> 1. Modify rebaseall and rebaselst to recognize 'eln' as a suffix and
>> to recognize the standard directory where emacs will install the
>> system-wide .eln files (corresponding to the preloaded libraries).
>
> That would be which directory?
When I build emacs from the upstream repo (without setting prefix) I see
ELN_DESTDIR='/usr/local/lib/emacs/28.0.50/
So I guess they will be in a subdirectory of /usr/lib/emacs when I build emacs
for Cygwin.
>> 2. Create a script /usr/bin/rebaselst_usr similar to rebaselst, with a
>> few modifications:
>>
>> a) All files are in the user's home directory:
>>
>> l=${HOME}/.config/rebase
>> b=${HOME}/.cache/rebase
>> db=${l}/dynpath.d
>
> …and there is this knotty problem. The user has one home directory, but
> she might be using many different hosts and both Cygwin architectures.
> The rebase information is host and architecture specific. I have no
> good solution for that yet and I don't know if XDG provides for that
> situation. Things might have to go into /var/run/user or some similar
> location instead. Note that the architecture dependence of eln (or
> really build dependence on a particular Emacs config if you want to be
> precise) already is a problem for Emacs in general and I haven't paid
> attention as to how they intend to solve that.
I haven't noticed any discussion of that. I don't know about dependence on a
particular Emacs config. But that was never an issue for elc files, so I doubt
if it's an issue for eln files. There's certainly architecture dependence, but
I don't think that will be a problem for us. If rebase encounters a library
intended for a different architecture, I think it will skip it, just as it skips
in-use files, won't it?
Ken
next prev parent reply other threads:[~2021-09-20 12:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4f799e88-40cd-2cdc-6d40-0285e66f5be0@cornell.edu>
[not found] ` <87o88pf5q1.fsf@Otto.invalid>
2021-09-19 12:37 ` Ken Brown
2021-09-19 16:39 ` Achim Gratz
2021-09-19 17:25 ` Ken Brown
2021-09-19 19:09 ` Achim Gratz
2021-09-19 22:24 ` Ken Brown
2021-09-20 5:58 ` ASSI
2021-09-20 12:57 ` Ken Brown [this message]
2021-09-22 21:21 ` Ken Brown
2021-09-23 17:34 ` Achim Gratz
2021-09-25 13:26 ` Achim Gratz
2021-09-25 15:37 ` Ken Brown
2021-09-25 15:45 ` Achim Gratz
2021-09-25 16:54 ` Ken Brown
2021-09-26 8:07 ` Achim Gratz
2021-09-26 23:17 ` Ken Brown
2021-09-27 6:43 ` ASSI
2021-09-27 12:48 ` Ken Brown
2021-09-27 13:21 ` ASSI
2021-09-27 21:48 ` Ken Brown
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=51a8043a-a8cb-840f-866e-53d64aac1ebe@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin-apps@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).