From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: steve tell Newsgroups: gmane.lisp.guile.user Subject: Re: Modified load-path proposal Date: Tue, 10 Jan 2006 23:49:59 -0500 (EST) Message-ID: References: <878xwx5ld2.fsf@ossau.uklinux.net> <87u0fl3wam.fsf@ossau.uklinux.net> <87oe5s51l4.fsf@ivanova.rotty.yi.org> <87ek6njah0.fsf@ossau.uklinux.net> <87r7adf8h1.fsf@zip.com.au> <87vezhbknv.fsf@ossau.uklinux.net> <87u0ey3mph.fsf@ossau.uklinux.net> <873bmf4ey4.fsf@laas.fr> <87y832l4af.fsf@ossau.uklinux.net> <87irttpf2c.fsf@laas.fr> <87r78duc9d.fsf@ossau.uklinux.net> <87hd99z7q2.fsf@laas.fr> <87bqyonopf.fsf@ossau.uklinux.net> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="-1463809024-503142642-1136954999=:22427" X-Trace: sea.gmane.org 1137004082 27780 80.91.229.2 (11 Jan 2006 18:28:02 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 11 Jan 2006 18:28:02 +0000 (UTC) Cc: guile-user@gnu.org Original-X-From: guile-user-bounces+guile-user=m.gmane.org@gnu.org Wed Jan 11 19:27:59 2006 Return-path: Envelope-to: guile-user@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1EwkhI-00007a-Jb for guile-user@m.gmane.org; Wed, 11 Jan 2006 19:27:48 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EwkjL-0008V3-AJ for guile-user@m.gmane.org; Wed, 11 Jan 2006 13:29:55 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1EwXy1-0006Ex-8A for guile-user@gnu.org; Tue, 10 Jan 2006 23:52:13 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1EwXy0-0006EY-Ko for guile-user@gnu.org; Tue, 10 Jan 2006 23:52:12 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EwXxx-0006EJ-0s for guile-user@gnu.org; Tue, 10 Jan 2006 23:52:09 -0500 Original-Received: from [66.93.240.80] (helo=ariel.telltronics.org) by monty-python.gnu.org with esmtp (TLS-1.0:DHE_RSA_3DES_EDE_CBC_SHA:24) (Exim 4.34) id 1EwY0V-0001o4-VC for guile-user@gnu.org; Tue, 10 Jan 2006 23:54:48 -0500 Original-Received: from ariel.telltronics.org (localhost.localdomain [127.0.0.1]) by ariel.telltronics.org (8.13.4/8.13.4) with ESMTP id k0B4o0dR007154; Tue, 10 Jan 2006 23:50:00 -0500 Original-Received: from localhost (tell@localhost) by ariel.telltronics.org (8.13.4/8.13.4/Submit) with ESMTP id k0B4nxIo007151; Tue, 10 Jan 2006 23:50:00 -0500 X-Authentication-Warning: ariel.telltronics.org: tell owned process doing -bs Original-To: Neil Jerram In-Reply-To: <87bqyonopf.fsf@ossau.uklinux.net> X-Mailman-Approved-At: Wed, 11 Jan 2006 12:36:15 -0500 X-BeenThere: guile-user@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General Guile related discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: guile-user-bounces+guile-user=m.gmane.org@gnu.org Errors-To: guile-user-bounces+guile-user=m.gmane.org@gnu.org Xref: news.gmane.org gmane.lisp.guile.user:5082 Archived-At: This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. ---1463809024-503142642-1136954999=:22427 Content-Type: TEXT/PLAIN; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by ariel.telltronics.org id k0B4o0dR007154 Just a little note to say that I've been following along and am glad this= =20 is being discussed - and of course a few comments. On Sat, 7 Jan 2006, Neil Jerram wrote: > ludovic.courtes@laas.fr (Ludovic Court=E8s) writes: > >> Neil Jerram writes: >> >>> How so? Given that you're about to do a (use-modules (whatnot)), I >>> can't see that also doing (initialize-packages "whatnot") will make a >>> significant difference. >> >> Because people haven't been doing so for years. Some of us certainly >> don't want to iterate over each and every Guile module to add this lin= e. I agree that an addition to the module-using or module-declaring=20 forms should be avoided. >> This is based on the observation that (i) we want modules to be >> installable in *any* directory, but (ii) at some point, there must be = a >> *fixed* directory to look for files to bootstrap further file loading. This general guideline seems to be on the right track: Lots of tools seem to have grown foo.conf.d directories, probably because= =20 they're friendly to package managers. Would a survey of conventions for such configuration-directories and how=20 they work be fruitful? One thing I notice is that systems where performance is important seem to "compile" the contents of the config=20 directory into a single file which can be read rapidly. Examples are /ld.so.conf.d incorporated into ld.so.cache by ldconfig, and Debian's update-modules building /etc/modules.conf from /etc/modutils. The guile analogy might be guile-config (a program run by=20 package-post-install scripts) collecting %load-path fragments from=20 $prefix/etc/guile-conf.d/* into $prefix/share/guile/config.scm (where $prefix is the prefix that guile was built with). guile-config could be little more than cat, or could do more complex=20 validation of the contents of each file in the config directory. Likely=20 it should remove duplicate %load-path entries, at least. But the scannin= g=20 of the directory is done only when needed, when a package containing a=20 guile module is added or removed. Important details to address: - how to control the order in which things appear in %load-path - how to make this play well with multiple versions of guile installed on= =20 the same system. > It seems to me that neither of these ideas (yours and mine) quite fly > yet. I have yet another idea, though, that I'll post in a separate > thread shortly. I'll look for that and keep reading. Thanks for thinking about this. My interest in part comes from maintaining a package that uses guile and=20 guile-gtk. It seems that most of my users' problems come when they try t= o=20 install guile-gtk from source (into /usr/local) but have guile installed=20 from their linux distribution (in /usr). My advice to date is generally to always install guile-gtk and guile in=20 the same way: either both from source (say into /usr/local) or to build=20 and install both using their package manager. Or else to become wizards=20 at setting up the right environment variables. But it would be nice if the more common case would just work. Steve ---1463809024-503142642-1136954999=:22427 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Guile-user mailing list Guile-user@gnu.org http://lists.gnu.org/mailman/listinfo/guile-user ---1463809024-503142642-1136954999=:22427--