unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Neil Jerram <neil@ossau.uklinux.net>
Cc: Guile Users <guile-user@gnu.org>
Subject: Re: Modified load-path proposal
Date: Thu, 13 Oct 2005 23:08:01 +0100	[thread overview]
Message-ID: <87u0fl3wam.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <rmiy84x9s6p.fsf@fnord.ir.bbn.com> (Greg Troxel's message of "13 Oct 2005 14:40:14 -0400")

Greg Troxel <gdt@ir.bbn.com> writes:

> We need remove-load-path too, for cleanup.

OK.

(Actually, "add" should probably be "ensure", and only add the
directory if not already in config; and "remove" should probably be
"cleanup", and only do anything if there is nothing left under the
relevant directory; but those are next-level details.)

> It's not clear to me how the default version of config shows up in a
> fresh guile build/install.  I'd argue that only the traditional three
> dirs in prefix should be there by default.

Yes, agreed.  (The default config.scm could be provided in the distro,
or could be generated during the make.)

>  Perhaps configure can have
> a "--add-load-path /usr/local/share/guile" to make the install search
> this, and this can be invoked by packaging systems that want it.  By

I don't think we need this, because it's equivalent to just running
guile-config add-load-path once after the install.

>   ;; 5. Code for GUILE_SCHEME_DIR autoconf macro
>
> This doesn't support the notion of putting things in
> $(prefix)/share/guile, and adding that to the load path of the
> existing guile when you do install.

Yes it does (I think).  If that's what you want, you just write your
Makefile.am like this ...

scmdatadir = $(datadir)/guile
scmdata_DATA = whatever1.scm whatever2.scm

... and add an extra install step (for which I forget the syntax)
that does

     guile-config add-load-path mydata $(datadir)/guile "My Location"

Am I still missing something?

>  Perhaps setting that up should be
> a standard pre-step before building the new package, but I believe
> that a package configured with --prefix=/usr/foo should only write to
> /usr/foo.  I realize others disagree, but I'd like the mechanisms to
> support this behavior.  perhaps the tag for /usr/foo/share/guile
> should be /usr/foo, so packages can search for a load dir by their
> prefix.  Perhaps there should be an optional argument that returns the
> path now and causes creation of it at make install time.

I don't see your point - can you be more concrete?

Thanks,
        Neil



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


  reply	other threads:[~2005-10-13 22:08 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-13 18:21 Modified load-path proposal Neil Jerram
2005-10-13 18:40 ` Greg Troxel
2005-10-13 22:08   ` Neil Jerram [this message]
2005-10-14  0:37     ` Greg Troxel
2005-10-14  1:28       ` Andreas Rottmann
2005-10-15 11:17         ` Neil Jerram
2005-10-15 15:03           ` Greg Troxel
2005-10-15 17:53             ` Neil Jerram
2005-10-22 23:16           ` Kevin Ryde
2005-10-28 17:45             ` Neil Jerram
2005-10-30 18:04               ` Neil Jerram
2005-10-30 18:15                 ` Tomas Zerolo
2005-10-30 20:37                 ` Thien-Thi Nguyen
2005-10-30 22:59                   ` Neil Jerram
2005-10-31 10:55                     ` Thien-Thi Nguyen
2005-10-31 19:22                       ` Neil Jerram
2005-11-08 12:37                         ` Thien-Thi Nguyen
2005-10-31 13:17                   ` Tomas Zerolo
2005-10-30 23:48                 ` Kevin Ryde
2005-10-31 13:20                   ` Tomas Zerolo
2005-10-31 19:20                   ` Neil Jerram
2005-10-31 23:54                     ` Kevin Ryde
2005-11-12  9:47                       ` Neil Jerram
2005-11-01 23:31                     ` Vorfeed Canal
2005-11-12 17:54                       ` Neil Jerram
2005-11-02  8:44                 ` Ludovic Courtès
2005-12-03 13:05                   ` Neil Jerram
2005-12-13  8:38                     ` Ludovic Courtès
2005-12-16  0:16                       ` Neil Jerram
2005-12-16  1:00                         ` Neil Jerram
2005-12-16  9:55                         ` Ludovic Courtès
2006-01-07 13:37                           ` Neil Jerram
2006-01-11  4:49                             ` steve tell
2006-01-12 18:01                               ` Neil Jerram
2005-10-15 11:24       ` Neil Jerram
2005-10-15 15:01         ` Greg Troxel
2005-10-15 17:49           ` Neil Jerram
2005-10-14  7:24 ` Ludovic Courtès
2005-10-15 11:55   ` Neil Jerram
2005-10-15 15:40     ` Greg Troxel
2005-10-17  8:04       ` Ludovic Courtès
2005-10-17 17:52         ` Greg Troxel
2005-10-18  8:23           ` Search path for C libraries Ludovic Courtès
2005-10-18 10:12             ` Vorfeed Canal
2005-10-17 17:54         ` Modified load-path proposal Neil Jerram
2005-10-18  7:57           ` Ludovic Courtès
2005-10-19 22:30             ` Neil Jerram
2005-10-20  7:56               ` Vorfeed Canal
2005-10-20  8:05               ` Ludovic Courtès
2005-10-20 22:23                 ` Neil Jerram
2005-10-21  7:59                   ` Ludovic Courtès
2005-10-17 18:10       ` Neil Jerram
2005-10-18 16:16         ` Greg Troxel
2005-10-18 21:24           ` Vorfeed Canal
2005-10-19 22:29           ` Neil Jerram

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=87u0fl3wam.fsf@ossau.uklinux.net \
    --to=neil@ossau.uklinux.net \
    --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).