[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: feature/package-vc has been merged
From: |
Eli Zaretskii |
Subject: |
Re: feature/package-vc has been merged |
Date: |
Sun, 06 Nov 2022 17:37:42 +0200 |
> From: Philip Kaludercic <philipk@posteo.net>
> Cc: monnier@iro.umontreal.ca, rms@gnu.org, emacs-devel@gnu.org
> Date: Sun, 06 Nov 2022 15:28:59 +0000
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> From: Philip Kaludercic <philipk@posteo.net>
> >> Cc: monnier@iro.umontreal.ca, rms@gnu.org, emacs-devel@gnu.org
> >> Date: Sun, 06 Nov 2022 11:43:15 +0000
> >>
> >> >> "Directory used to store clone repositories.
> >> >>
> >> >> This directory is only used for packages with a special `:lisp-dir'
> >> >> entry in their package specification (for details on package
> >> >> specifications see `package-vc-selected-packages'). Repositories for
> >> >> packages like these are cloned into the directory specified here, and
> >> >> their `:lisp-dir' is then linked back into the user elpa directory."
> >> >
> >> > Instead of "specified here", please use "specified by this variable".
> >> > And I don't think I understand what the "their `:lisp-dir' is then
> >> > linked back into the user elpa directory" part wants to say.
> >>
> >>
> >>
> >> > 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.
- feature/package-vc has been merged, Philip Kaludercic, 2022/11/04
- Re: feature/package-vc has been merged, Stefan Monnier, 2022/11/04
- Re: feature/package-vc has been merged, Eli Zaretskii, 2022/11/05
- Re: feature/package-vc has been merged, Philip Kaludercic, 2022/11/05
- Re: feature/package-vc has been merged, Eli Zaretskii, 2022/11/05
- Re: feature/package-vc has been merged, Philip Kaludercic, 2022/11/06
- Re: feature/package-vc has been merged, Eli Zaretskii, 2022/11/06
- Re: feature/package-vc has been merged, Philip Kaludercic, 2022/11/06
- Re: feature/package-vc has been merged,
Eli Zaretskii <=
- Re: feature/package-vc has been merged, Philip Kaludercic, 2022/11/06
- Re: feature/package-vc has been merged, Eli Zaretskii, 2022/11/06
- Re: feature/package-vc has been merged, Philip Kaludercic, 2022/11/06
- Re: feature/package-vc has been merged, Eli Zaretskii, 2022/11/06
- Re: feature/package-vc has been merged, Philip Kaludercic, 2022/11/06
- Re: feature/package-vc has been merged, Eli Zaretskii, 2022/11/06
- Re: feature/package-vc has been merged, Philip Kaludercic, 2022/11/06
- Re: feature/package-vc has been merged, Eli Zaretskii, 2022/11/06
- Re: feature/package-vc has been merged, Philip Kaludercic, 2022/11/07
- Re: feature/package-vc has been merged, Eli Zaretskii, 2022/11/07