From: Eli Zaretskii <eliz@gnu.org>
To: Glenn Morris <rgm@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Links emacs -> emacs-NN.MM.KK
Date: Sun, 07 Apr 2013 05:51:54 +0300 [thread overview]
Message-ID: <83mwtbcat1.fsf@gnu.org> (raw)
In-Reply-To: <5sli8vsax1.fsf@fencepost.gnu.org>
> From: Glenn Morris <rgm@gnu.org>
> Cc: emacs-devel@gnu.org
> Date: Sat, 06 Apr 2013 15:42:50 -0400
>
> Eli Zaretskii wrote:
>
> > Why do we create a hard link emacs -> emacs.NN.MM.KK when dumping in
> > the src directory, but a symbolic link in "make install"? Why the
> > difference?
>
> We use a symlink when installing if configure says they are supported.
> It just seems like the right thing to do in that case (makes it more
> obvious what is going on, people in the past have been confused about
> why bin/emacs was getting "installed twice", etc).
>
> It's a relatively recent change to do so rather than use a hard link.
> Either I forgot to consider src/Makefile at that time, or decided it
> wasn't worth bothering to change that part, or decided there was some
> reason not to.
It's not in src/Makefile, it's in loadup.el, whicvh uses
add-name-to-file.
> Such a reason would be if we delete one end of the link and still
> expect the other to work. I'm afraid I don't remember which of these
> explanations applies, sorry.
OK, thanks. So it shouldn't be a problem if the Windows build uses a
hard link in this case, I think, or a copy if the filesystem is FAT32
that doesn't support hard links. Creating symlinks is a PITA on
Windows, as they require privileges and pop up UAC prompts.
prev parent reply other threads:[~2013-04-07 2:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-06 18:41 Links emacs -> emacs-NN.MM.KK Eli Zaretskii
2013-04-06 19:42 ` Glenn Morris
2013-04-07 2:51 ` Eli Zaretskii [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=83mwtbcat1.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rgm@gnu.org \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.