From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: vbuaraujo@sapo.pt Newsgroups: gmane.lisp.guile.user Subject: Re: How to make GNU Guile more successful Date: Fri, 10 Mar 2017 14:27:35 +0000 Message-ID: <20170310142735.Horde.LUkzcGBtiLQRiGdA2WIxdfF@mail.sapo.pt> References: <58C20A87.9010908@sapo.pt> <877f3xfo6f.fsf@web.de> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes Content-Transfer-Encoding: 8bit X-Trace: blaine.gmane.org 1489156090 12132 195.159.176.226 (10 Mar 2017 14:28:10 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 10 Mar 2017 14:28:10 +0000 (UTC) User-Agent: IMP PTMail 5.12.21 To: guile-user@gnu.org Original-X-From: guile-user-bounces+guile-user=m.gmane.org@gnu.org Fri Mar 10 15:28:05 2017 Return-path: Envelope-to: guile-user@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cmLWU-0002LO-3a for guile-user@m.gmane.org; Fri, 10 Mar 2017 15:28:02 +0100 Original-Received: from localhost ([::1]:39396 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cmLWZ-0002Xf-Q4 for guile-user@m.gmane.org; Fri, 10 Mar 2017 09:28:07 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:40916) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cmLWB-0002XW-JQ for guile-user@gnu.org; Fri, 10 Mar 2017 09:27:44 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cmLW7-0005cx-Ge for guile-user@gnu.org; Fri, 10 Mar 2017 09:27:43 -0500 Original-Received: from relay3.ptmail.sapo.pt ([212.55.154.23]:38569 helo=sapo.pt) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1cmLW7-0005bw-4l for guile-user@gnu.org; Fri, 10 Mar 2017 09:27:39 -0500 Original-Received: (qmail 2486 invoked from network); 10 Mar 2017 14:27:35 -0000 Original-Received: from [::ffff:201.86.238.42] ([::ffff:201.86.238.42]) by mail.sapo.pt (Horde Framework) with HTTPS; Fri, 10 Mar 2017 14:27:35 +0000 In-Reply-To: X-Originating-IP: ::ffff:201.86.238.42 X-PTMail-Version: PTMail 5.12.21 X-PTMail-User: eyJpdiI6ImpnSklGMzB0UXBzV2xXZHpjN3cxSlE9PSIsImQiOiI4M29oMm5yUGMreHdRSGZkalpwZkJOaUpQNGdqT3hVZGFNQTFURUJGKzdnPSJ9 Content-Disposition: inline X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy] X-Received-From: 212.55.154.23 X-BeenThere: guile-user@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: General Guile related discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guile-user-bounces+guile-user=m.gmane.org@gnu.org Original-Sender: "guile-user" Xref: news.gmane.org gmane.lisp.guile.user:13477 Archived-At: Citando Panicz Maciej Godek : > 2017-03-10 10:55 GMT+01:00 Arne Babenhauserheide : > >> >> Vítor De Araújo writes: >> >> > (Or maybe package _names_ could be URLs pointing to an index in a >> > well-defined format, which tells how to download each version of a >> > package; then we could have even dependency management without a >> > central repository. I'm pipe-dreaming here, though.) >> >> You’re not just dreaming: >> >> https://github.com/plande/compan/blob/master/compan.scm >> >> ;; clone the repository and load (lib) module from the top level: >> (load-modules ("https://bitbucket.org/panicz/dogma" (lib))) >> >> ;; as above, but load modules from "libraries" directory: >> (load-modules (("https://github.com/panicz/pamphlet" "libraries") >> (pamphlet))) >> >> ;; one can also fix on a particular tag/branch/commit: >> (load-modules (("https://bitbucket.org/panicz/dogma" "." >> "3884445191c2") (lib))) >> >> We’d just have to decide to use this. That's very cool :) And also supports my point that there should be something like a wiki for publishing information about Guile packages. It'd be hard for me to find this on my own. >> I think that the situation isn't quite as good as one could think. The > code works fine from > the interpreter, but if fails to work for compiled code, and I think that > we'd need to come up > with some solution of delaing module imports in compiled code until they're > available. > > (Note also that the source code of Compan is extremely straightforward, as > it boils down > to a few calls of the "system" function which in turns calls some "hg" > commands) > > So while I think that the author's idea was very nice, it clearly needs > some elaboration :) Yeah, for one I don't think the URLs should go directly into the code, but rather in a package metadata file. The reason is I don't think we should hard-code the package manager in the code. People should be able to use the code without having the package manager, if they already have the dependencies installed by some other means. But the basic idea is cool. :) -- Vítor De Araújo