From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Alex Sassmannshausen Newsgroups: gmane.lisp.guile.user Subject: Re: [ANN] Guile Hall Release (v0.1.1) Date: Mon, 02 Jul 2018 11:39:21 +0200 Message-ID: <871scmugc6.fsf@gmail.com> References: <8736x3upkx.fsf@gmail.com> <1830482f737675b99bcb1f3c2231c1fe@hypermove.net> Reply-To: alex.sassmannshausen@gmail.com NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: blaine.gmane.org 1530524355 32106 195.159.176.226 (2 Jul 2018 09:39:15 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 2 Jul 2018 09:39:15 +0000 (UTC) User-Agent: mu4e 1.0; emacs 26.1 Cc: guile-user@gnu.org, guile-user To: Amirouche Boubekki Original-X-From: guile-user-bounces+guile-user=m.gmane.org@gnu.org Mon Jul 02 11:39:11 2018 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 1fZvIb-0008F0-NR for guile-user@m.gmane.org; Mon, 02 Jul 2018 11:39:09 +0200 Original-Received: from localhost ([::1]:59673 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fZvKj-0007ge-1q for guile-user@m.gmane.org; Mon, 02 Jul 2018 05:41:21 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:43790) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fZvIv-0006Vx-Do for guile-user@gnu.org; Mon, 02 Jul 2018 05:39:30 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fZvIu-0007g7-By for guile-user@gnu.org; Mon, 02 Jul 2018 05:39:29 -0400 Original-Received: from mail-ed1-x529.google.com ([2a00:1450:4864:20::529]:33670) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fZvIr-0007em-Mo; Mon, 02 Jul 2018 05:39:25 -0400 Original-Received: by mail-ed1-x529.google.com with SMTP id l23-v6so11253010edq.0; Mon, 02 Jul 2018 02:39:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=references:user-agent:from:to:cc:subject:reply-to:in-reply-to:date :message-id:mime-version:content-transfer-encoding; bh=ofiX9xK5Q/BBBJgW4s2eGvtk/3afIu8yG0pNW1eH5b8=; b=MGWvZociatwp1Ag1B66Dyko050X8iiHON+HPRs1NtUOfesm71J3CtfwgyO0JldQjyM uj/prz9HvAu1H48lQyj4a/te551RGh2OUZ8Jqhy6fN/uY1lfI0VTlBGvtZGgXs0f5Vca N87JLFmYxMsWN/jrZviJDxrsvcsFko006qXwenFAH2gM3XBMQO4ZOuJvxu0IXsokk5IK VMMBhBO2m471VkvbJcqbl6z1kE2klABtbCWbspaxQxYtPflbjGzjUObE2VHSI2rq5Ntg iX6KVrONkPs+EP4fhUT9Noh/JodfHHiZD0jOGE33rB3qBeenIksmz4XEQFdOxxHq+/bZ KmdQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:references:user-agent:from:to:cc:subject :reply-to:in-reply-to:date:message-id:mime-version :content-transfer-encoding; bh=ofiX9xK5Q/BBBJgW4s2eGvtk/3afIu8yG0pNW1eH5b8=; b=FStW4+pZcKzrF8DJhV0qYPItCTcc2SV7UdTi3Dx6C6saX8keer8nLy+kfgw8JCCtKx yOmO80gdPh6w71ecmDJQKLNR327jXWDLBpmXzCNaeLLJ3IMxjxsWofLVUtPlZ3ul0T74 PKXZt17YloHeDVICq172Tn2BX829oCAKz1u+WlMm1I6kzfpifpA2sIJoo7tOBdpGTHCG qqSz977Z0mwD+lvZPdwPCtZ0PSiX4J/ZbZh4TEb82hXahLmGLyZvO9vQm//NDj6hpYwu pkNYFo4SO1NQw4pYd0Vp7AndBuxScVgcrJZEgU2CAZYkTDT4fBH+s6pGYBnndWM305Ys oRxQ== X-Gm-Message-State: APt69E3s0qlcG8Tfl003kxXNTdH+Oon3TJwLJ/W1vVd118f/B2KMJBqf xeRCxRzZYECENBNjS4iOkzLqTZhB X-Google-Smtp-Source: AAOMgpfnXU3zUoO/mVsaYeihjwtQAgrmzUXMxnYMszV4XLVsMI2H+nFzXhBM8HAug/Y1eFE4l3njZQ== X-Received: by 2002:a50:a0c5:: with SMTP id 63-v6mr7579293edo.47.1530524364151; Mon, 02 Jul 2018 02:39:24 -0700 (PDT) Original-Received: from rosser ([2a02:a03f:5304:5b00:6694:cb83:72e4:dd02]) by smtp.gmail.com with ESMTPSA id m6-v6sm2798802ede.61.2018.07.02.02.39.23 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Mon, 02 Jul 2018 02:39:23 -0700 (PDT) In-reply-to: <1830482f737675b99bcb1f3c2231c1fe@hypermove.net> X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2a00:1450:4864:20::529 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:14674 Archived-At: Hi Amirouche, Amirouche Boubekki writes: > On 2018-07-01 14:07, Alex Sassmannshausen wrote: >> Hello, >> >> It is with great trepidation and joy that I finally release Hall to the >> world. >> >> You can get it with Guix after pulling the latest version with >> $ guix package -i guile-hall >> >> Otherwise you can get the code from >> https://gitlab.com/a-sassmannshausen/guile-hall/, and build (hopefully) >> using the traditional > > This is nicely put. I will try to use to port the work I've done in chez > and compare both approaches or maybe bundle guile-web with it. > > Do you recommend rebasing a project that has already autotools support > to use hall? It depends=E2=80=A6 On the one hand, if: - you are comfortable with autotools - your project includes non-guile modules that need to be installed - your project has a complicated project hierarchy Then it might not be worth using Hall. In the last case you might still use Hall to generate Guix files, but to be honest, that doesn't gain you much. On the other hand, if: - your autotools-fu is cargo-culty (like mine is) - your project is Guile only - you find the steps of maintaining the autotools infrastructure and rolling releases a pain Then you might well benefit from switching to Hall. It is definitely possible to use hand-written configure.ac files & Makefile.am files with Hall: it simply does not touch those files. On the other hand, one of the nice things about Hall is that you can regenerate a lot of the "infrastructure" files easily (autotools, basic documentation, guix), and that feature obviously becomes more attractive if you fully convert to the Hall way. In any case, if you do want to give it a go, you probably want to use $ hall init --convert [project-name] --author=3D$author It will output the files to be generated, have a look whether that seems sensible, then run with the --execute flag to create the files. Then open the generated hall.scm file and try to map your project folder-hierarchy to the files section. Alternatively you could give $ hall scan a shot. It will try to generate a new hall.scm file on the basis of your project hierarchy =E2=80=94 bit it may fail to do so. You can then run with --execute if you actually want to update your hall.scm file. I would suggest, play around. Though you'll probably find it way more satisfying to use from the get go in a new project as you get the expected user journey. > Thanks for sharing! My pleasure :) Alex