all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Abdorhman Ayman <Abdorhman.Ayman@protonmail.com>
Cc: 49878@debbugs.gnu.org
Subject: bug#49878: Emacs Tarball Should Include Uninstall Script
Date: Thu, 05 Aug 2021 13:09:26 +0200	[thread overview]
Message-ID: <87sfzognbt.fsf@gnus.org> (raw)
In-Reply-To: <Aw6hsn50vU2Z4XKRKLIKIhhczUqdjuVLFjg18HH1ZRHLPLbWrxvcjUcVW-dNfZiw_8otoDl4SXL7G29D_appciOpd2hMRtijFC_KVnlgxyw=@protonmail.com> (Abdorhman Ayman's message of "Wed, 04 Aug 2021 16:45:09 +0000")

Abdorhman Ayman <Abdorhman.Ayman@protonmail.com> writes:

> Someone on Debian forums encountered a system issue after compiling
> Emacs 27.2 from source, he suspects that his issue MAYBE related to Emacs,
> or maybe it's not, it doesn't really matter, what matters is that his report
> brought to my attention that Emacs tarball doesn't include an uninstall
> script. We need an uninstall script for user convenience.

I'm not sure an uninstall script is practical -- we can't just delete
the files with the same names as those we installed, because we don't
know whether they're the same ones (or something added later by the
user).

I've never understood why any user would say "make install" at all --
Emacs works just fine without saying "make install".  Users should just
run it from where it was compiled.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2021-08-05 11:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-04 16:45 bug#49878: Emacs Tarball Should Include Uninstall Script Abdorhman Ayman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-08-05 11:09 ` Lars Ingebrigtsen [this message]
2021-08-05 11:25   ` Eli Zaretskii
2021-08-06  9:37     ` Lars Ingebrigtsen
2021-08-06 11:11       ` Eli Zaretskii
2021-08-06 11:32         ` 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=87sfzognbt.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=49878@debbugs.gnu.org \
    --cc=Abdorhman.Ayman@protonmail.com \
    /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.