From: Divya Ranjan <divya@subvertising.org>
To: guix-devel@gnu.org
Cc: Robert Smith <robertsmith@posteo.net>
Subject: On updating anki to latest Qt version
Date: Tue, 12 Nov 2024 12:44:28 +0000 [thread overview]
Message-ID: <87y11ooc43.fsf@subvertising.org> (raw)
Hello Robert and others,
Checking the logs, I found that you added Anki in Feb (8534c94). As a regular user of anki, I found that the one provided by Guix is simply too old, almost 5 years old. The index of the downloads doesn’t even show 2.1.16. The comment in /gnu/packages/education.scm shows:
#+begin_src scheme
(define-public anki
(package
(name "anki")
;; Later versions have dependencies on npm packages not yet in Guix.
(version "2.1.16")
(source ...))
#+end_src
I haven’t checked all the versions, but the latest version of Anki _does not_ seem to have any npm dependencies. The official development instructions [0] do not mention anything about npm, and the Linux Specific notes [1] only mention that node binary is a prerequisite, which seems to be already packaged in guix.
Other guides [2] do not seem to need any npm either, I’ve known that it’s been notoriously difficult to package anki into distros [3,4], but I _believe_ (I’m not sure), things have changed since they switched from Bazel back to Ninja build system?
I’d like some work on this, I want to rely on flatpak as less I can.
[0]: https://github.com/ankitects/anki/blob/main/docs/development.md
[1]: https://github.com/ankitects/anki/blob/main/docs/linux.md
[2]: https://chrislongros.com/2023/03/23/how-to-build-anki-from-source-in-linux/
[3]: https://github.com/ankitects/anki/issues/1378
[4]: https://forums.ankiweb.net/t/need-support-for-building-packaging/41892/5
Regards,
--
Divya Ranjan,
Philosophy, Mathematics, Libre Software.
reply other threads:[~2024-11-12 12:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87y11ooc43.fsf@subvertising.org \
--to=divya@subvertising.org \
--cc=guix-devel@gnu.org \
--cc=robertsmith@posteo.net \
/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).