From: Hoshpak <Hoshpak@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: transmission: build with cmake
Date: Mon, 01 Jun 2020 10:01:20 +0200 [thread overview]
Message-ID: <20200601080120.jgyWHwUtwuFIlyImZXi1TqdfP_TbN1qN7xDjTLiYOYs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-22373@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 968 bytes --]
There's a merged pull request on the void-packages repository
transmission: build with cmake
https://github.com/void-linux/void-packages/pull/22373
Description:
Creating a second PR which fixes cross builds. Sorry for polluting the PR queue.
- Updated template to use `build_style=cmake` instead of `gnu-configure`. This is because upstream recommends building with `cmake` and localisation doesn't work with `gnu-configure`.
- Fixed broken Qt translations from previous revision
Right now the official tarball from [transmission/transmission-releases](https://github.com/transmission/transmission-releases) is broken as mentioned in [this issue](https://github.com/transmission/transmission/issues/1248). User @floppym has rolled their own tarball with [this fix](https://github.com/transmission/transmission/pull/1247) applied. I have used that tarball for now but hopefully we can revert to official tarballs for future versions.
Thanks a lot @floppym
prev parent reply other threads:[~2020-06-01 8:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-28 7:57 [PR PATCH] " kartikynwa
2020-05-31 15:35 ` [PR PATCH] [Updated] " kartikynwa
2020-05-31 15:48 ` kartikynwa
2020-05-31 15:57 ` [PR PATCH] [Updated] " kartikynwa
2020-05-31 15:58 ` kartikynwa
2020-05-31 16:14 ` floppym
2020-05-31 16:15 ` [PR PATCH] [Updated] " kartikynwa
2020-06-01 8:01 ` Hoshpak [this message]
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=20200601080120.jgyWHwUtwuFIlyImZXi1TqdfP_TbN1qN7xDjTLiYOYs@z \
--to=hoshpak@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).