public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: ASSI <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: autorebase and user-installed dynamic objects
Date: Sun, 19 Sep 2021 08:18:46 +0200	[thread overview]
Message-ID: <87o88pf5q1.fsf@Otto.invalid> (raw)
In-Reply-To: <4f799e88-40cd-2cdc-6d40-0285e66f5be0@cornell.edu> (Ken Brown via Cygwin's message of "Sat, 18 Sep 2021 18:51:31 -0400")

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.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Wavetables for the Terratec KOMPLEXER:
http://Synth.Stromeko.net/Downloads.html#KomplexerWaves

      reply	other threads:[~2021-09-19  6:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-18 22:51 Ken Brown
2021-09-19  6:18 ` ASSI [this message]

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=87o88pf5q1.fsf@Otto.invalid \
    --to=stromeko@nexgo.de \
    --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).