git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: tony.luck@gmail.com
Cc: git@vger.kernel.org
Subject: Re: Add uninstall target to Makefile
Date: Fri, 16 Sep 2005 11:01:19 -0700	[thread overview]
Message-ID: <7v1x3oopsg.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <12c511ca0509161021249c89a9@mail.gmail.com> (Tony Luck's message of "Fri, 16 Sep 2005 10:21:25 -0700")

Tony Luck <tony.luck@gmail.com> writes:

> Perhaps it would be easier[1] to support "make obsolete-uninstall"
> that would remove
> objects installed by previous generations of git?
>
> -Tony
>
> [1] easier, nicer, cleaner, less detestable, whatever.

And how far back a release should we keep track of the name of
obsolete versions?  /usr/bin/git-uninstall for each particular
version that knows what that version ships _might_ make some
sense, but I do not see much point in having uninstall target in
the Makefile.  Should one be allowed to run make uninstall with
bindir or DESTDIR set to different values from the ones used
when 'make install' was run the last time?  What about things
like "make WITH_SEND_MAIL=YesPlease install"?

Guys, packaged distributions know how to remove obsolete
binaries.  OTOH if you are building from the source and
installing, you are the only one who knows what you are
installing and where.

      parent reply	other threads:[~2005-09-16 18:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-16 12:58 Add uninstall target to Makefile Martin Atukunda
2005-09-16 17:08 ` Junio C Hamano
2005-09-16 17:54   ` John W. Linville
2005-09-16 18:08     ` Chris Wright
2005-09-16 19:19       ` John W. Linville
2005-09-16 23:05         ` Junio C Hamano
2005-09-16 23:37           ` Johannes Schindelin
2005-09-18 10:03       ` Martin Atukunda
     [not found]   ` <12c511ca0509161021249c89a9@mail.gmail.com>
2005-09-16 18:01     ` Junio C Hamano [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=7v1x3oopsg.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=git@vger.kernel.org \
    --cc=tony.luck@gmail.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).