public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: cygwin-apps <cygwin-apps@cygwin.com>
Subject: Re: autorebase and user-installed dynamic objects
Date: Sun, 19 Sep 2021 08:37:25 -0400	[thread overview]
Message-ID: <48f41125-8eaa-2f9e-9835-67deaa2d2ff3@cornell.edu> (raw)
In-Reply-To: <87o88pf5q1.fsf@Otto.invalid>

[Redirected from the main Cygwin list.]

On 9/19/2021 2:18 AM, ASSI wrote:
> Ken Brown via Cygwin writes:
>> 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,
> 
> That's how it was originally intended to work, IIRC (but the
> documentation indeed wrongly suggests to put paths there).  Obviously
> since we didn't have that situation before I never fully tested and
> completed this part.
> 
>> 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?
> 
> For reasons I don't exactly remember, I wanted to avoid that.  Probably
> because the user directory might not be available or accessible for the
> install user, but then obviously you'd just as likely have a problem
> with the actual rebasing also.  I've been mulling the idea of having
> user specific rebase databases on top of the system one (or more
> generally a hierarchy of rebase DB) several times and that's one of the
> reasons they might be needed.
> 
> Let's discuss how this can and should work on cygwin-apps.

A per-user database sounds like a good idea.

Ken

       reply	other threads:[~2021-09-19 12:37 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 [this message]
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
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=48f41125-8eaa-2f9e-9835-67deaa2d2ff3@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).