[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug#36919] [PATCH 1/2] gnu-maintenance: KDE updater no longer relies on
[bug#36919] [PATCH 1/2] gnu-maintenance: KDE updater no longer relies on FTP access.
Sun, 01 Sep 2019 21:43:51 +0200
Gnus/5.13 (Gnus v5.13) Emacs/26.2 (gnu/linux)
Hartmut Goebel <address@hidden> skribis:
>> How about moving this code to (guix import kde) as was done for (guix
>> import gnome) when we discussed it back then? (See
> I'll be fine with this.
> I just wonder whether we/I should refactor the new code to be more
> flexible for other ls-lR cases and keep the common parts in
> gnu-maintenance.scm. OTOH currently there is no other use-case
Yeah, we’d have to identify what common parts exist. On IRC we discussed
utility procedures like ‘file-sans-extension’, which would be worth
Other things may not be good candidates—for instance, the GNU thing is
probably close to what you’d write for KDE, but it’s still not exactly
the same. Since there’s usually fine-tuning to be done, it may be best
to keep them separate.
> 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?
Oh I see. You could roughly have one procedure for each clause and
chain them. A macro might help make that more readable (Clojure has
|[Prev in Thread]
||[Next in Thread]|
- [bug#36919] [PATCH 1/2] gnu-maintenance: KDE updater no longer relies on FTP access.,
Ludovic Courtès <=