unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: rm@fabula.de
Cc: ttn@glug.org, a.rottmann@gmx.at, mvo@zagadka.ping.de,
	neil@ossau.uklinux.net, guile-devel@gnu.org, guile-user@gnu.org
Subject: Re: [d.love@dl.ac.uk: dynamic loading of native code modules]
Date: Wed, 24 Apr 2002 16:51:30 +0200	[thread overview]
Message-ID: <20020424145130.GC17392@www> (raw)
In-Reply-To: <87662hkvya.fsf@raven.i.defaultvalue.org>

On Wed, Apr 24, 2002 at 09:33:33AM -0500, Rob Browning wrote:
> Thien-Thi Nguyen <ttn@giblet.glug.org> writes:
> 
> > well i raised this point two (3?) years ago and the counter-point
> > was that all shared object libraries are the same and should be
> > treated the same.  of course, this is not entirely true; all the
> > object libraries we're interested in playing w/ via a scheme
> > interface must depend on libguile, minimally, and are loaded into a
> > more restricted environment than say "appfoo dynloads libbar.so".
> 
> And if we put them in some non-lib dir, do you propose that we
> internally mangle the user's LD_LIBRARY_PATH in order to allow ldso to
> find the libs?  Many people consider this unacceptable application
> behavior, so that's another point that somewhat weighs in favor of
> using the standard directories.

I'd say "follow the masses". What  do applications like Apache, Perl,
Python etc. do? They all come with their 'private' locations for
application specific libraries (let's call them plug-ins, since this
seems to describe their function).
Why is manipulation of an _applications_ LD_LIBRARY_PATH an un-
acceptable behaviour (only applications exec'ed by guile would 
notice this, anyway) ?
 
> Also, you do have to worry about distribution packaging systems --
> make sure that everyone's going to be ok, inter-package
> dependency-wise with us placing libs in non-standard locations.

Again, it doesn't seem to be a problem in other languages that support
FFI. One _major_ benefit would be the possibility to have multiple versions
of guile not interfere with each other. As an example:
 i currently have both /usr/lib/python1.5, /usr/lib/python2.0 and
 /usr/lib/python2.1 on my box. Trying to do the same with guile turned
 out to be rather complex.

 Ralf Mattes

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


  reply	other threads:[~2002-04-24 14:51 UTC|newest]

Thread overview: 65+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-12  1:06 [d.love@dl.ac.uk: dynamic loading of native code modules] Thien-Thi Nguyen
2002-04-13  8:50 ` Neil Jerram
2002-04-14  0:58   ` Rob Browning
2002-04-14 22:22     ` Neil Jerram
2002-04-15  4:21       ` Rob Browning
2002-04-16 20:23         ` Neil Jerram
2002-04-17  5:25           ` Rob Browning
2002-04-20  8:14           ` Thien-Thi Nguyen
2002-04-20 11:07             ` Neil Jerram
2002-04-15 12:15       ` Marius Vollmer
2002-04-16 20:24         ` Neil Jerram
2002-04-17  0:53           ` NIIBE Yutaka
2002-04-20  7:57             ` Thien-Thi Nguyen
2002-04-17  5:36           ` Rob Browning
2002-04-17  5:43             ` Rob Browning
2002-04-20  7:53             ` Thien-Thi Nguyen
2002-04-21 15:20               ` Rob Browning
2002-04-21 15:51                 ` Robert A. Uhl
2002-04-21 16:27                   ` Rob Browning
2002-05-14  8:53                 ` Thien-Thi Nguyen
2002-04-14 21:30   ` Marius Vollmer
2002-04-15 17:58     ` Andreas Rottmann
2002-04-15 19:06       ` Marius Vollmer
2002-04-24  8:00       ` Thien-Thi Nguyen
2002-04-24 14:33         ` Rob Browning
2002-04-24 14:51           ` rm [this message]
2002-04-24 15:14             ` Andreas Rottmann
2002-04-24 15:48               ` Rob Browning
2002-04-24 16:15                 ` Bill Gribble
2002-04-24 16:24                   ` Rob Browning
2002-04-24 18:10                   ` Andreas Rottmann
2002-04-24 20:36                     ` Rob Browning
     [not found]                     ` <87wuuwhm08.fsf@raven.i.defaultvalue.org>
2002-04-25  2:05                       ` Joshua Judson Rosen
2002-04-25  3:03                         ` Rob Browning
2002-04-24 18:06                 ` Andreas Rottmann
2002-04-24 20:40                   ` Rob Browning
2002-04-24 20:53                     ` Andreas Rottmann
2002-04-30  0:26                     ` Lynn Winebarger
2002-04-30  1:35                       ` Thien-Thi Nguyen
2002-04-30  2:33                         ` Lynn Winebarger
     [not found]                         ` <0204292133140I.10649@locke.free-expression.org>
2002-05-04  0:19                           ` Thien-Thi Nguyen
2002-04-30  0:20                 ` Lynn Winebarger
2002-04-24 15:28             ` Rob Browning
2002-05-15  0:19               ` Thien-Thi Nguyen
2002-04-24 18:34           ` Thien-Thi Nguyen
2002-04-24 18:58             ` Rob Browning
2002-04-25  5:32               ` Thien-Thi Nguyen
2002-05-01  5:00           ` Lynn Winebarger
2002-05-01 13:50             ` Rob Browning
2002-04-24  0:52     ` Thien-Thi Nguyen
2002-04-20  9:06   ` Thien-Thi Nguyen
2002-04-20 12:21     ` Neil Jerram
2002-04-20 12:44       ` Thien-Thi Nguyen
2002-04-24  0:09   ` Thien-Thi Nguyen
2002-04-14  0:34 ` Rob Browning
2002-04-14  2:55   ` Rob Browning
2002-04-24  0:24   ` Thien-Thi Nguyen
2002-04-24  5:25     ` Rob Browning
2002-04-24 21:18       ` Marius Vollmer
2002-04-25  4:10         ` Thien-Thi Nguyen
2002-04-28 15:32           ` Marius Vollmer
2002-04-28 20:19             ` Thien-Thi Nguyen
2002-05-14 10:57       ` Thien-Thi Nguyen
2002-05-14 16:11         ` Bill Gribble
2002-05-14 20:54           ` Thien-Thi Nguyen

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=20020424145130.GC17392@www \
    --to=rm@fabula.de \
    --cc=a.rottmann@gmx.at \
    --cc=guile-devel@gnu.org \
    --cc=guile-user@gnu.org \
    --cc=mvo@zagadka.ping.de \
    --cc=neil@ossau.uklinux.net \
    --cc=ttn@glug.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).