unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Lynn Winebarger <owinebar@free-expression.org>
Subject: Re: Guile 1.5.8 beta available for testing.
Date: Thu, 29 Aug 2002 14:24:45 -0500	[thread overview]
Message-ID: <0208291424451K.19624@locke.free-expression.org> (raw)
In-Reply-To: <0208291417451J.19624@locke.free-expression.org>

On Thursday 29 August 2002 14:17, Lynn Winebarger wrote:
> On Thursday 29 August 2002 13:55, Marius Vollmer wrote:
> > Rob Browning <rlb@defaultvalue.org> writes:
> > > I think we'd hoped to wait until 1.7 development to try to come up
> > > with a more correct solution, but it *is* a little awkward to
> > > require people to set envt vars just to run guile when they're
> > > installing to /usr/local.
> > 
> > Yes, one option would be to make libltdl parse /etc/ld.so.conf on
> > systems that have it.
> > 
> > On the other hand, you have to set PATH already, why not also
> > LD_LIBRARY_PATH?  It would be system wide, or session wide setting,
> > not a per-process setting.
> 
>      The problem is for people who muddle with several development projects
> at once.  You might want to test development versions of both libfoo and the
> libfoo dependent appbar concurrently in /usr/local, but still want appbar to 
> use the stable version of libfoo in /usr/lib because appbar has enough instability 
> of its own.
> 
      I forgot to mention: You also want the stable appbar that lives in /usr
to use the stable version of libfoo.

Lynn


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


  reply	other threads:[~2002-08-29 19:24 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-26 17:34 Guile 1.5.8 beta available for testing Rob Browning
2002-08-27  9:06 ` Lars J. Aas
2002-08-28 16:28   ` Marius Vollmer
2002-08-29  7:59     ` Lars J. Aas
2002-08-31 12:01       ` Marius Vollmer
2002-09-02 11:38         ` Lars J. Aas
2002-08-29 10:29 ` tomas
2002-08-29 16:22   ` Rob Browning
2002-08-29 17:18     ` tomas
2002-08-29 17:42     ` tomas
2002-08-29 17:49       ` Rob Browning
2002-08-29 18:04         ` Lynn Winebarger
2002-08-29 18:55         ` Marius Vollmer
2002-08-29 19:17           ` Lynn Winebarger
2002-08-29 19:24             ` Lynn Winebarger [this message]
2002-08-29 19:58             ` Marius Vollmer
2002-08-31 16:45       ` tomas
2002-08-29 18:49     ` Marius Vollmer
  -- strict thread matches above, loose matches on Subject: below --
2002-08-28 13:34 Sven Hartrumpf
2002-08-28 14:21 ` Marius Vollmer
2002-08-28 14:38   ` Sven Hartrumpf
2002-08-28 15:34     ` Marius Vollmer
2002-08-28 16:21       ` Lynn Winebarger
2002-08-28 18:18     ` Han-Wen Nienhuys
2002-08-28 21:09       ` Sven Hartrumpf
2002-08-28 22:43         ` Han-Wen Nienhuys
2002-09-03  7:33         ` Sven Hartrumpf
2002-09-04 11:08           ` Han-Wen Nienhuys
2002-09-04 14:43             ` Sven Hartrumpf
2002-09-05 12:08               ` Han-Wen Nienhuys
2002-09-05 19:52                 ` Sven Hartrumpf
2002-09-03 11:14       ` Sven Hartrumpf

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=0208291424451K.19624@locke.free-expression.org \
    --to=owinebar@free-expression.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).