unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Tim McNamara <timmcn@bitstream.net>
Subject: Re: Installation Question
Date: Thu, 11 Dec 2003 13:37:51 -0600	[thread overview]
Message-ID: <m2n09z9mcw.fsf@bitstream.net> (raw)
In-Reply-To: mailman.1597.1071171490.399.help-gnu-emacs@gnu.org

exits funnel <exitsfunnel@yahoo.com> writes:

> The result seems to be that the new version is resting in
> /usr/local/bin but /usr/bin which is first in my path so when I try
> to run emacs I'm still getting the old one.  I realize I could swap
> the order of the directories in my path but I'm wondering what the
> conventional solution is?  Should I just remove the version in
> /usr/local/bin?

No, that's the one you want to be running.  One potential approach-
not saying this is the correct or best one- is to change the name of
/usr/bin/emacs (e.g., 'mv /usr/bin/emacs old.emacs') and then create a
link in /usr/bin called 'emacs' that links to /usr/local/bin/emacs
which is your shiny new version. I don't know the correct syntax for
this in Linux, it's a little different than in BSDish Unixen IIRC.

> What's the difference between /usr/local/bin and /usr/bin anyway?
> Should the install script have copied 21.3 to /usr/local/bin?

/usr/bin is for system-installed binaries, whereas /usr/local/bin is
for user install binaries (or so I've been told).  Often 'make
install' puts new software in /usr/local/bin to avoid overwriting the
old software.

  parent reply	other threads:[~2003-12-11 19:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1597.1071171490.399.help-gnu-emacs@gnu.org>
2003-12-11 19:33 ` Installation Question Jesper Harder
2003-12-11 19:37 ` Tim McNamara [this message]
2003-12-11 20:01 ` Dan Anderson
2003-12-11 20:02 ` Martin Stemplinger
2003-12-11 18:35 exits funnel

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m2n09z9mcw.fsf@bitstream.net \
    --to=timmcn@bitstream.net \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).