From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: 74702@debbugs.gnu.org, Vivien Kraus <vivien@planete-kraus.eu>
Subject: [bug#74702] [PATCH 4/4] gnu: Add komikku-servers.
Date: Tue, 10 Dec 2024 20:54:04 +0100 [thread overview]
Message-ID: <a0410b1bee58c24d1b88af89c3cf57c6c0258958.camel@gmail.com> (raw)
In-Reply-To: <87h67ditcr.fsf@gmail.com>
Am Montag, dem 09.12.2024 um 09:37 +0900 schrieb Maxim Cournoyer:
> Hello,
>
> Liliana Marie Prikler <liliana.prikler@gmail.com> writes:
>
> > * gnu/packages/gnome.scm (komikku-servers): New variable.
> > ---
> > gnu/packages/gnome.scm | 36 ++++++++++++++++++++++++++++++++++++
> > 1 file changed, 36 insertions(+)
> >
> > diff --git a/gnu/packages/gnome.scm b/gnu/packages/gnome.scm
> > index ae0e1f4783..3c89ab4054 100644
> > --- a/gnu/packages/gnome.scm
> > +++ b/gnu/packages/gnome.scm
> > @@ -233,6 +233,7 @@ (define-module (gnu packages gnome)
> > #:use-module (gnu artwork)
> > #:use-module (guix build-system cargo)
> > #:use-module (guix build-system cmake)
> > + #:use-module (guix build-system copy)
> > #:use-module (guix build-system glib-or-gtk)
> > #:use-module (guix build-system gnu)
> > #:use-module (guix build-system meson)
> > @@ -13647,6 +13648,41 @@ (define-public komikku
> > (variable "KOMIKKU_SERVERS_PATH")
> > (files
> > '("lib/komikku/servers")))))))
> >
> > +(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 :)
> > + (source
> > + (origin
> > + (method git-fetch)
> > + (uri (git-reference
> > + (url "https://codeberg.org/valos/Komikku/")
> > + (commit (string-append "v" version))))
> > + (file-name (git-file-name name version))
> > + (sha256
> > + (base32
> > +
> > "0sfqmqcpdl3bsbs0wxl4jwvd7wpgigkvvasy1niz6qm2vnp35gzq"))))
> > + (build-system copy-build-system)
> > + (arguments
> > + (list
> > + #:install-plan
> > + #~'(("komikku/servers" "lib/komikku/servers"))
> > + #:modules '((guix build copy-build-system)
> > + (guix build utils)
> > + (ice-9 ftw))
> > + #:phases
> > + #~(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.
Cheers
¹ Komikku uses a custom module loader I once wrote that was upstreamed
some time ago, which means we can control the search path freely. I
chose a directory that does not rely on Python to avoid any potential
conflict here.
next prev parent reply other threads:[~2024-12-10 19:55 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 4/4] gnu: Add komikku-servers Liliana Marie Prikler
2024-12-09 0:37 ` Maxim Cournoyer
2024-12-10 19:54 ` Liliana Marie Prikler [this message]
2024-12-11 2:40 ` Maxim Cournoyer
2024-12-05 16:50 ` [bug#74702] [PATCH 2/4] gnu: Add python-pillow-heif 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
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=a0410b1bee58c24d1b88af89c3cf57c6c0258958.camel@gmail.com \
--to=liliana.prikler@gmail.com \
--cc=74702@debbugs.gnu.org \
--cc=maxim.cournoyer@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.