From: 0x5c <0x5c@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: helvum: update to 0.4.1.
Date: Sun, 17 Sep 2023 10:13:33 +0200 [thread overview]
Message-ID: <20230917081333.A-cuwhlFuHOwQCZOfQoy5IoNkQkLElC9YKro5NHtDE8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46082@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 770 bytes --]
New comment by 0x5c on void-packages repository
https://github.com/void-linux/void-packages/pull/46082#issuecomment-1722421440
Comment:
> A bit tangential, this template uses the `cargo` build style instead of the `meson` one and recommends checking all `meson.build` files during each update. I think this is probably not the ideal approach so I had these changes when I updated it locally a few months ago.
The meson story is a pure nuisance for downstream packagers, since all it does is a couple of template filling operations *and things that should only run on the end-user system* in xbps triggers. The reason upstream has it is so that `meson install` does the desktop db update on gnome systems for users that manually build helvum, and for flatpack dist.
next prev parent reply other threads:[~2023-09-17 8:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-16 10:14 [PR PATCH] " 0x5c
2023-09-16 11:54 ` tranzystorek-io
2023-09-16 12:32 ` 0x5c
2023-09-16 15:18 ` [PR PATCH] [Updated] " 0x5c
2023-09-16 15:33 ` 0x5c
2023-09-17 2:54 ` 0x5c
2023-09-17 6:15 ` icp1994
2023-09-17 8:13 ` 0x5c [this message]
2023-09-17 8:13 ` 0x5c
2023-09-17 8:18 ` 0x5c
2023-09-17 10:43 ` icp1994
2023-09-18 7:55 ` 0x5c
2023-09-18 7:55 ` 0x5c
2023-09-20 12:14 ` [PR PATCH] [Updated] " 0x5c
2023-09-20 12:27 ` 0x5c
2023-09-20 12:29 ` 0x5c
2023-09-26 18:10 ` [PR PATCH] [Updated] " 0x5c
2023-09-26 18:20 ` [PR PATCH] [Merged]: " classabbyamp
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=20230917081333.A-cuwhlFuHOwQCZOfQoy5IoNkQkLElC9YKro5NHtDE8@z \
--to=0x5c@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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.
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 NNTP newsgroup(s).