From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Simon Tournier <zimon.toutoune@gmail.com>, 73073@debbugs.gnu.org
Cc: Vivien Kraus <vivien@planete-kraus.eu>,
Maxim Cournoyer <maxim.cournoyer@gmail.com>
Subject: [bug#73073] [PATCH 4/6] gnu: gnome-recipes: Move libgd origin from phases to native-inputs.
Date: Fri, 06 Sep 2024 19:33:26 +0200 [thread overview]
Message-ID: <f1357ec8c534073231b92e7d4c455e2fce6f2db4.camel@gmail.com> (raw)
In-Reply-To: <4b84954a845391197ebbdbb7f5c9d04eb3ecdc7f.1725636992.git.zimon.toutoune@gmail.com>
Am Freitag, dem 06.09.2024 um 17:54 +0200 schrieb Simon Tournier:
> * gnu/packages/dlang.scm (gnome-recipes)[arguments]<phases>: Move
> libgd
> origin from here...
> [native-inputs]: ...to here.
>
> Change-Id: I137dc41819a680fdf1f5c0bea9778b2bceae3fad
> ---
> gnu/packages/gnome.scm | 22 ++++++++++++----------
> 1 file changed, 12 insertions(+), 10 deletions(-)
>
> diff --git a/gnu/packages/gnome.scm b/gnu/packages/gnome.scm
> index 7339000436..8ae9fb0656 100644
> --- a/gnu/packages/gnome.scm
> +++ b/gnu/packages/gnome.scm
> @@ -799,15 +799,7 @@ (define-public gnome-recipes
> (add-after 'unpack 'unpack-libgd
> (lambda _
> (copy-recursively
> - #$(origin
> - (method git-fetch)
> - (uri (git-reference
> - (url
> "https://gitlab.gnome.org/GNOME/libgd")
> - (commit
> "c7c7ff4e05d3fe82854219091cf116cce6b19de0")))
> - (file-name (git-file-name "libgd" version))
> - (sha256
> - (base32
> -
> "16yld0ap7qj1n96h4f2sqkjmibg7xx5xwkqxdfzam2nmyfdlrrrs")))
> + #$(this-package-native-input "libgd")
> "subprojects/libgd"))))))
> (inputs (list glib
> gnome-autoar
> @@ -823,7 +815,17 @@ (define-public gnome-recipes
> `(,glib "bin")
> itstool
> pkg-config
> - python))
> + python
> + `("libgd"
> + ,(origin
> + (method git-fetch)
> + (uri (git-reference
> + (url
> "https://gitlab.gnome.org/GNOME/libgd")
> + (commit
> "c7c7ff4e05d3fe82854219091cf116cce6b19de0")))
> + (file-name (git-file-name "libgd"
> version))
> + (sha256
> + (base32
I can see why you're doing that, but I'm not really convinced it helps
the package. Particularly, we're now even adding a labeled input,
which makes for a cursed situation where all but one inputs are
unlabeled¹.
IMHO, G-Expressions in phases serve in part to facilitate uses like
this. They may not be nice, but those are upstream conditions we have
to cope with. I'd rather do a proper unbundling of libgd.
Another "proper" solution could be as easy as using an unlabeled origin
and search-input-file. However, this doesn't really work all that well
if you have to unpack the entire origin, hence what I've done here for
gnome-recipes.
Cheers
¹ Let's not even mention the necessity of 1/6 to enable that. Back in
the day, there was a decision against giving origins labels because it
would add to the further propagation of label use throughout Guix,
while we want to drop them.
next prev parent reply other threads:[~2024-09-06 17:35 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-06 15:51 [bug#73073] [PATCH 0/6] Allow origin with label as inputs Simon Tournier
2024-09-06 15:54 ` [bug#73073] [PATCH 1/6] guix: packages: " Simon Tournier
2024-09-06 15:54 ` [bug#73073] [PATCH 2/6] gnu: dmd-bootstrap: Move phobos origin from phases to native-inputs Simon Tournier
2024-09-06 15:54 ` [bug#73073] [PATCH 3/6] gnu: smithforth: Move system.fs " Simon Tournier
2024-09-06 15:54 ` [bug#73073] [PATCH 4/6] gnu: gnome-recipes: Move libgd " Simon Tournier
2024-09-06 17:33 ` Liliana Marie Prikler [this message]
2024-09-06 18:11 ` Simon Tournier
2024-09-06 20:14 ` Liliana Marie Prikler
2024-09-07 11:37 ` Simon Tournier
2024-09-06 15:54 ` [bug#73073] [PATCH 5/6] gnu: farstream: Move common " Simon Tournier
2024-09-06 15:54 ` [bug#73073] [PATCH 6/6] gnu: gnulib: Move phobos " Simon Tournier
2024-09-06 21:45 ` [bug#73073] [PATCH 0/6] Allow origin with label as inputs Ludovic Courtès
2024-09-07 13:40 ` Simon Tournier
2024-09-07 14:49 ` Liliana Marie Prikler
2024-09-16 20:13 ` Ludovic Courtès
2024-09-10 1:27 ` [bug#73073] [PATCH v2 0/8] Allow origin inside inputs with "new style" Simon Tournier
2024-09-10 1:27 ` [bug#73073] [PATCH v2 1/8] guix: packages: " Simon Tournier
2024-09-16 20:19 ` Ludovic Courtès
2024-09-16 20:42 ` Simon Tournier
2024-09-26 13:30 ` Maxim Cournoyer
2024-09-10 1:27 ` [bug#73073] [PATCH v2 2/8] gnu: gnome-recipes: Move libgd origin from phases to native-inputs Simon Tournier
2024-09-10 4:30 ` Liliana Marie Prikler
2024-09-10 7:58 ` Simon Tournier
2024-09-10 1:27 ` [bug#73073] [PATCH v2 3/8] gnu: dmd-bootstrap: Move phobos " Simon Tournier
2024-09-10 1:27 ` [bug#73073] [PATCH v2 4/8] gnu: smithforth: Move system.fs " Simon Tournier
2024-09-10 1:27 ` [bug#73073] [PATCH v2 5/8] gnu: farstream: Move common " Simon Tournier
2024-09-10 1:27 ` [bug#73073] [PATCH v2 6/8] gnu: gnulib: Move phobos " Simon Tournier
2024-09-10 1:27 ` [bug#73073] [PATCH v2 7/8] gnu: git: Move git-manpages " Simon Tournier
2024-09-10 1:27 ` [bug#73073] [PATCH v2 8/8] gnu: cgit: Remove input labels Simon Tournier
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f1357ec8c534073231b92e7d4c455e2fce6f2db4.camel@gmail.com \
--to=liliana.prikler@gmail.com \
--cc=73073@debbugs.gnu.org \
--cc=maxim.cournoyer@gmail.com \
--cc=vivien@planete-kraus.eu \
--cc=zimon.toutoune@gmail.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).