From: Jaft <jaft.r@outlook.com>
To: "60294@debbugs.gnu.org" <60294@debbugs.gnu.org>,
Liliana Marie Prikler <liliana.prikler@gmail.com>
Subject: [bug#60294] [PATCH] gnu: Add libxapp.
Date: Sat, 24 Dec 2022 11:23:37 +0000 (UTC) [thread overview]
Message-ID: <BY5PR07MB702991C35E3780D3A3534E8099EE9@BY5PR07MB7029.namprd07.prod.outlook.com> (raw)
In-Reply-To: <d2275b0a35253929184daa4eca9dcbc5344fde8c.camel@gmail.com>
On Saturday, December 24, 2022 at 04:36:02 AM CST, Liliana Marie Prikler <liliana.prikler@gmail.com> wrote:
Am Samstag, dem 24.12.2022 um 01:30 -0600 schrieb Wamm K. D:
> > + (substitute* "pygobject/meson.build"
> > + (("get_option[(]'py-overrides-dir'[)]")
> > + (string-append "'"
> > + (assoc-ref outputs "out")
> > + "/lib/python"
> > + #$(version-major+minor (package-
> > version python))
> > + "/site-packages/gi/overrides'")))
> I think python-build-system has a function to get this version in a
> more reliable way.
Would you possibly know any more details on it? Just looking through the module, I don't see any functions regarding version number, I'm afraid, and it's not intuitive to me how I might use it in this context if I'm using a different build system for the package.
> > + (("'/usr/bin/pastebin'") (string-append "'"
> > + (assoc-ref
> > outputs "out")
> > +
> > "/bin/pastebin'"))
> Oof, fine, but note that you can also write #$output
Fair; I'd thought about it but the example I was working off of was using G-expressions and did it this way so I just went with it.
Something I've wondered: is there a point to having the lambda arguments be "#:key outputs", if you can just use "#$output"? I've seen a few setup their lambda that way only to use "#$output" and not ever use "outputs".
I may just be missing something regarding G-expressions, though.
> > + (synopsis "Cross-desktop libraries and common resources for X-
> > apps")
> > + (description
> > + "The components which are common to multiple GTK desktop
> > environments
> > +(Cinnamon, MATE and Xfce) and required to implement cross-DE
> > solutions.")
> The description should consist of full sentences.
> Also, since X-Apps are quite specific to Linux Mint, you should
> probably not take folks knowing what they are for granted.
True but is there any easy way to specify what they're related to without making it much longer than just a synopsis?
"Cross-desktop libraries and common resources" can apply to many things and is generic to the point of being unhelpful, I'd think.
I could always do "developed by Linux Mint" instead of "for X-apps" which might be more familiar but, again, it borders to being unhelpfully unspecific, again (even if less so), to me; there are probably a lot of "Cross-desktop libraries and common resources" developed by Linux Mint. This particular library was developed for use with the X-apps they're developing, specifically.
I'm just not sure what other description would work while still being a synopsis.
> > + (license license:lgpl3)))
> No +?
Mmm; I didn't think so but you raise a good point. Lemme double check myself; I'll adjust it, if otherwise.
next prev parent reply other threads:[~2022-12-24 11:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-24 7:30 [bug#60294] [PATCH] gnu: Add libxapp Wamm K. D
2022-12-24 10:35 ` Liliana Marie Prikler
2022-12-24 11:23 ` Jaft [this message]
2022-12-24 14:13 ` 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
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=BY5PR07MB702991C35E3780D3A3534E8099EE9@BY5PR07MB7029.namprd07.prod.outlook.com \
--to=jaft.r@outlook.com \
--cc=60294@debbugs.gnu.org \
--cc=liliana.prikler@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).