From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>
Cc: vivien@planete-kraus.eu, 75167@debbugs.gnu.org
Subject: [bug#75167] [PATCH gnome-team 1/6] gnu: Add libpeas-2.
Date: Sun, 29 Dec 2024 12:29:37 +0900 [thread overview]
Message-ID: <87y0zzgo9q.fsf@gmail.com> (raw)
In-Reply-To: <f06380bc0347bf30b6a22a1a7772696ed0bfebfa.1735418244.git.liliana.prikler@gmail.com> (Liliana Marie Prikler's message of "Sat, 28 Dec 2024 20:22:21 +0100")
Hi Liliana,
Liliana Marie Prikler <liliana.prikler@gmail.com> writes:
> * gnu/packages/gnome.scm (libpeas-2): New variable.
[...]
> +(define-public libpeas-2
> + (package
[...]
> + "Libpeas is a gobject-based plugin engine, targeted at giving every
> +application the chance to assume its own extensibility. It also has a set of
> +features including, but not limited to: multiple extension points; on-demand
> +(lazy) programming language support for C, Python and JS; simplicity of the
> +API.")
> + (license license:lgpl2.0+)))
> +
> (define-public libpeas
> (package
> (name "libpeas")
Is a new package really required? Could we instead more simply update
libpeas directly to version 2? If the older libpeas need to be
maintained, I think inheriting from the older version would make sense
to avoid duplicated fields.
--
Thanks,
Maxim
next prev parent reply other threads:[~2024-12-29 3:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-28 20:37 [bug#75167] [PATCH gnome-team 0/6] Update GNOME Builder to 47.2 Liliana Marie Prikler
2024-12-28 19:22 ` [bug#75167] [PATCH gnome-team 1/6] gnu: Add libpeas-2 Liliana Marie Prikler
2024-12-29 3:29 ` Maxim Cournoyer [this message]
2024-12-28 19:22 ` [bug#75167] [PATCH gnome-team 2/6] gnu: jsonrpc-glib: Update to 3.44.1 Liliana Marie Prikler
2024-12-28 19:23 ` [bug#75167] [PATCH gnome-team 3/6] gnu: libdex: Update to 0.8.1 Liliana Marie Prikler
2024-12-28 20:34 ` [bug#75167] [PATCH gnome-team 4/6] gnu: gom: Update to 0.5.3 Liliana Marie Prikler
2024-12-28 20:34 ` [bug#75167] [PATCH gnome-team 5/6] gnu: Add libspelling Liliana Marie Prikler
2024-12-29 4:34 ` Maxim Cournoyer
2024-12-28 20:35 ` [bug#75167] [PATCH gnome-team 6/6] gnu: gnome-builder: Update to 47.2 Liliana Marie Prikler
2024-12-29 4:38 ` Maxim Cournoyer
2024-12-29 4:38 ` [bug#75167] [PATCH gnome-team 0/6] Update GNOME Builder " Maxim Cournoyer
2024-12-29 8:31 ` bug#75167: " Liliana Marie Prikler
2024-12-30 2:49 ` [bug#75167] " 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
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=87y0zzgo9q.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=75167@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 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).