A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://lists.gnu.org/archive/html/emacs-devel/2022-11/msg00355.html below:

Re: feature/package-vc has been merged

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] From: Philip Kaludercic Subject: Re: feature/package-vc has been merged Date: Sun, 06 Nov 2022 15:58:11 +0000 
Eli Zaretskii <eliz@gnu.org> writes:

>> >> > I also have a more general question: you say this "is only used
>> >> > for
>> >> > packages with a special `:lisp-dir' entry", and that begs the
>> >> > question: where will we clone a package that doesn't have the
>> >> > :lisp-dir entry?
>> >> 
>> >> Directly into the elpa directory.
>> >
>> > And the "linked back" means a symlink? or something else?
>> 
>> Right.  If the package specification has a custom lisp directory, clone
>> the directory elsewhere and will then symlink [actual repo] + [lisp
>> dir]
>> into ~/.config/emacs/elpa (or whatever directory is used).
>> 
>> > Anyway, I think all of this should be explained in the doc string.
>> 
>> Will do.
>
> And symlinks could be problematic on MS-Windows.  Maybe allow to copy
> instead.

That I did not know.  The issue with copying is that you loose vc
information.

When do symlinks create issues under windows?

Perhaps there is a better way to solve this issue in general?  I would
have to look at how complicated it would be to make package.el load a
subdirectory instead of the immediate directory under "elpa".

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4