unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Byron Hale <byron.hale@einfo.com>
Cc: guile-user@gnu.org
Subject: Re: Problems making & installing Guile 1.4
Date: Tue, 23 Apr 2002 15:11:17 -0700	[thread overview]
Message-ID: <5.1.0.14.2.20020423150120.02a94e90@einfo.com> (raw)
In-Reply-To: <20020417154024.GA1274@www>

At 05:40 PM 4/17/2002 +0200, you wrote:
>...
>The usual thing to do is to have /usr/local/bin *before* /usr/bin
>in your $PATH (you set that in your $HOME/.bash_profile; for a
>global setting, i.e. for all users, you'd edit /etc/profile).
>
>This way, things you install under /usr/local take precedence
>over things pre-installed in /usr, which is usually what you
>want. Your mileage might vary, of course.
>
>For root it's different. There, security considerations are
>more important than ease of use.

Actually, my own, non-root, account has the ordering that you mentioned.
I'm afraid to tinker with root's path ordering, so I'm leaving it as is.

Apparently I installed Guile 1.3 in January or February as a general good
idea and renaming 1.3 hasn't hurt me so far. Using Guile as a shell,
given that it will be made more consistent and not so dependent on
whitespace placement, etc.,  seems an excellent idea to me.

I studied SICP using Scheme and miss its continuations in SML97 and
Haskell98. I'll be following this list with interest now.

 > At any rate, Guile 1.4 is up and running. Thanks!
>Good news, then!
>Regards
>-- tomas

Byron




_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user


      parent reply	other threads:[~2002-04-23 22:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-18  7:39 Problems making & installing Guile 1.4 Byron Hale
2002-04-16  9:20 ` tomas
2001-08-19 11:18   ` Byron Hale
     [not found] ` <20020417154024.GA1274@www>
2002-04-23 22:11   ` Byron Hale [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

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

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

  git send-email \
    --in-reply-to=5.1.0.14.2.20020423150120.02a94e90@einfo.com \
    --to=byron.hale@einfo.com \
    --cc=guile-user@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.
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).