all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 36919@debbugs.gnu.org
Subject: [bug#36919] [PATCH 1/2] gnu-maintenance: KDE updater no longer relies on FTP access.
Date: Tue, 27 Aug 2019 10:30:32 +0200	[thread overview]
Message-ID: <80cc20cb-589b-30df-4a3e-896a21d42eba@crazy-compilers.com> (raw)
In-Reply-To: <87k1bbcxrc.fsf@gnu.org>

Hi Ludo,

thanks for the coding advice. This was what I've been asking for :-)
Just one point:

Am 17.08.19 um 23:01 schrieb Ludovic Courtès:
> As a rule of thumb we don’t use ‘set!’ in Guix, except in special
> circumstances.  In this case you can write:
>
>   (define (canonicalize-path path)
>     (cond ((string-prefix? …)
>            (string-drop path 17))
>           ((string-suffix? …)
>            (string-drop-right path 1))
>           …))

AFAIK, `cond` only processes the first expression where `test ` is true.
In this case, we need to process *all* cases where the test is true.
This means we need to nest the evaluation, which is ugly and hard to
read IMHO. Is there some more "linear" syntax?

(BTW: The manual [1] is not quite precise on `cond`, so I needed to test
it. Maybe I did it wrong.)

[1] https://www.gnu.org/software/guile/manual/html_node/Conditionals.html

-- 
Regards
Hartmut Goebel

| Hartmut Goebel          | h.goebel@crazy-compilers.com               |
| www.crazy-compilers.com | compilers which you thought are impossible |

  parent reply	other threads:[~2019-08-27  8:31 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-04 10:25 [bug#36919] [PATCH 0/2] Make the KDE updater find packaes in subdirectories Hartmut Goebel
2019-08-04 10:28 ` Hartmut Goebel
2019-08-04 10:28   ` [bug#36919] [PATCH 1/2] gnu-maintenance: KDE updater no longer relies on FTP access Hartmut Goebel
2019-08-17 21:01     ` Ludovic Courtès
2019-08-27  8:11       ` Hartmut Goebel
2019-09-01 19:43         ` Ludovic Courtès
2019-08-27  8:30       ` Hartmut Goebel [this message]
2019-08-04 10:28   ` [bug#36919] [PATCH 2/2] gnu-maintenance: KDE updater finds packages even in sub-directory Hartmut Goebel
2019-09-03 12:24 ` [bug#36919] [Patch v2 0/4] Make the KDE updater find packages in subdirectories Hartmut Goebel
2019-09-03 12:24   ` [bug#36919] [Patch v2 1/4] guix: Rename and move sans-extension to tarball-sans-extension Hartmut Goebel
2019-09-03 12:24   ` [bug#36919] [Patch v2 2/4] gnu-maintenance: KDE updater no longer relies on FTP access Hartmut Goebel
2019-09-03 12:24   ` [bug#36919] [Patch v2 3/4] upstream: Move KDE updater into a separate module Hartmut Goebel
2019-09-03 12:24   ` [bug#36919] [Patch v2 4/4] import: KDE updater finds packages even in sub-directory Hartmut Goebel
2019-09-09 22:44   ` [bug#36919] [Patch v2 0/4] Make the KDE updater find packages in subdirectories Ludovic Courtès
2019-09-10 17:09     ` bug#36919: " Hartmut Goebel

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=80cc20cb-589b-30df-4a3e-896a21d42eba@crazy-compilers.com \
    --to=h.goebel@crazy-compilers.com \
    --cc=36919@debbugs.gnu.org \
    --cc=ludo@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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.