emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Easy configuration of a site-lisp directory


From: Arthur Miller
Subject: Re: Easy configuration of a site-lisp directory
Date: Sat, 21 Aug 2021 16:34:34 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux)

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Arthur Miller <arthur.miller@live.com>
>> Date: Sat, 21 Aug 2021 05:12:25 +0200
>> Cc: Philip Kaludercic <philipk@posteo.net>, emacs-devel@gnu.org
>> 
>> After some search, yes seems like symlinks are not so great on Windows:
>> 
>> https://blogs.windows.com/windowsdeveloper/2016/12/02/symlinks-windows-10/
>> 
>> Don't udnerstand why are symlinks such a big deal for them.
>
> They are deemed to be a security vulnerability in some quarters,
> because they can potentially circumvent access rights.

I understand they consider it a security issue, but I don't understand
why. Couldn't they apply same rules to symlinked file access as if the
access was direct? Bit I guess Microsoft has acquired quite clever
people so they have their reasons. I don't think they removed symlinks
just because, for no good reason.

I would rather be interesting what elpa-admin.el does. As I looked it up
today, there is a 2k lines file in elpa sources, I guess Stefan means
that one?

Is it going to become part of Emacs, or he just means that
developers should use it develop packages, or why do you bring it up? I
sincerely have never used it, so I wonder how does it relate to normal
users who wish to manage their site-lisp with pacakge.el. Obviously from
what Philip posted, and from what I see on Reddit and elsewhere, there
is appeal in just cloning a git repo and bringing it into Emacs. I am
not sure if it is the best practice, but I do understand the appeal and
that is obviously what makes people prefer some other package
managers. So is this elpa-admin.el soemthing that addresses that
convenience/workflow or do you plan something else for package.el?



reply via email to

[Prev in Thread] Current Thread [Next in Thread]