all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>
Cc: 74702@debbugs.gnu.org, Vivien Kraus <vivien@planete-kraus.eu>
Subject: [bug#74702] [PATCH 4/4] gnu: Add komikku-servers.
Date: Wed, 11 Dec 2024 11:40:55 +0900	[thread overview]
Message-ID: <87ikrrgcw8.fsf@gmail.com> (raw)
In-Reply-To: <a0410b1bee58c24d1b88af89c3cf57c6c0258958.camel@gmail.com> (Liliana Marie Prikler's message of "Tue, 10 Dec 2024 20:54:04 +0100")

Hi,

Liliana Marie Prikler <liliana.prikler@gmail.com> writes:

[...]

>> > +(define-public komikku-servers
>> > +  (package
>> > +    (name "komikku-servers")
>> > +    (version "1.59.0")                  ; latest version that
>> > works with 1.57
>> 
>> Per our referenced Scheme coding style [0] in (info '(guix)
>> Formatting Code'), the space between ';' and the comment for inline
>> comments can be omitted (see the '** Comments' section).
>> 
>> [0]  https://mumble.net/~campbell/scheme/style.txt
> I read this 'can' as optional and very much prefer my space :)

It's indeed a 'can', but I value consistency enough that this errs on
the side of 'should' in my mind ;-).

[...]

>> > +      #~(modify-phases %standard-phases
>> > +          (add-after 'unpack 'delete-conflicting-files
>> > +            (lambda _
>> > +              (with-directory-excursion "komikku/servers"
>> > +                (for-each delete-file
>> > +                          (scandir "."
>> > +                                   (lambda (f) (string-suffix?
>> > ".py" f))))))))))
>> 
>> Shouldn't these Python files be byte-compiled?  You could perhaps use
>> the compile-bytecode phase from the pyproject-build-system to
>> accomplish that.
> I can't use it verbatim, since the install directory is different¹, but
> I can copy it's logic, sure.  Will do so for v2.

OK.  If it's too much boilerplate to copy-paste, feel free to ignore it.
It's probably not world-changing anyway.

-- 
Thanks,
Maxim

  reply	other threads:[~2024-12-11  2:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-05 16:50 [bug#74702] [PATCH 0/4] Update komikku to 1.57.0 Liliana Marie Prikler
2024-12-05 16:50 ` [bug#74702] [PATCH 1/4] gnu: python-pillow: Update to 11.0.0 Liliana Marie Prikler
2024-12-05 16:50 ` [bug#74702] [PATCH 3/4] gnu: komikku: Update to 1.57.0 Liliana Marie Prikler
2024-12-09  0:31   ` Maxim Cournoyer
2024-12-05 16:50 ` [bug#74702] [PATCH 4/4] gnu: Add komikku-servers Liliana Marie Prikler
2024-12-09  0:37   ` Maxim Cournoyer
2024-12-10 19:54     ` Liliana Marie Prikler
2024-12-11  2:40       ` Maxim Cournoyer [this message]
2024-12-05 16:50 ` [bug#74702] [PATCH 2/4] gnu: Add python-pillow-heif Liliana Marie Prikler

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=87ikrrgcw8.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=74702@debbugs.gnu.org \
    --cc=liliana.prikler@gmail.com \
    --cc=vivien@planete-kraus.eu \
    /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.