From: danjenson <danjenson@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: update of anki
Date: Wed, 26 Jan 2022 02:02:46 +0100 [thread overview]
Message-ID: <20220126010246.ti2yMcs-SCgLkW5V5OOCz55fCIxFkpRk2jghEkivoPA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35238@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1204 bytes --]
There's a closed pull request on the void-packages repository
update of anki
https://github.com/void-linux/void-packages/pull/35238
Description:
tl;dr, the build system seems to have switched to bazel, but I don't see this as a `build_style` option. This is my first attempt at updating a package. Anki has had a great many releases since the current void version, and appears to host it's source files on github now.
#### Testing the changes
- I tested the changes in this PR: NO, I could not figure out how to get the bazel build system to function on void
<!--
#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): TBD, will check once I can get it compiled
-->
<!-- Note: If the build is likely to take more than 2 hours, please [skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration)
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, x86-64
-->
prev parent reply other threads:[~2022-01-26 1:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-25 22:26 [PR PATCH] " danjenson
2022-01-25 23:09 ` paper42
2022-01-26 1:02 ` danjenson
2022-01-26 1:02 ` danjenson [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=20220126010246.ti2yMcs-SCgLkW5V5OOCz55fCIxFkpRk2jghEkivoPA@z \
--to=danjenson@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).