From: Eli Zaretskii <eliz@gnu.org>
To: phillip.lord@russet.org.uk (Phillip Lord)
Cc: 22935@debbugs.gnu.org
Subject: bug#22935: W32 Binaries should have a top-level directory
Date: Tue, 08 Mar 2016 20:52:32 +0200 [thread overview]
Message-ID: <838u1sredr.fsf@gnu.org> (raw)
In-Reply-To: <87fuw2m1pr.fsf@russet.org.uk> (phillip.lord@russet.org.uk)
> From: phillip.lord@russet.org.uk (Phillip Lord)
> Date: Mon, 07 Mar 2016 21:12:48 +0000
>
> I would suggest that future Emacs zip files contain a top-level
> directory with the same name as the zip file, underneath which comes
> /var, /share, /bin, plus README.W32, plus COPYING. This still makes it
> easily to install over an existing distribution with a copy command.
I don't quite agree with the last sentence. There's no 'cp' on
Windows out of the box, so either people will use XCOPY or the Windows
Explorer. Both will by default nag users about overwriting existing
files in the destination, and not everyone will know how to work
around that.
Besides, I think most people will simply leave the files in the
directory where they were unpacked, and will then have to play with
their PATH or rename the top-level directory.
By contrast, if the zip archive does NOT have a top-level directory,
it is easy to create one upon unpacking: the 'unzip' command has the
"-d" switch for that, and unpacking from Explorer will actually
suggest a separate directory by default.
next prev parent reply other threads:[~2016-03-08 18:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-07 21:12 bug#22935: W32 Binaries should have a top-level directory Phillip Lord
2016-03-08 18:52 ` Eli Zaretskii [this message]
2016-03-08 19:35 ` Phillip Lord
2016-03-08 20:01 ` Eli Zaretskii
2021-08-15 12:44 ` Lars Ingebrigtsen
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=838u1sredr.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=22935@debbugs.gnu.org \
--cc=phillip.lord@russet.org.uk \
/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.