From: Daniel Buschke <damage@devloop.de>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] TIDAL ebuild
Date: Tue, 24 Dec 2024 15:11:40 +0100 [thread overview]
Message-ID: <dbcc2d0a-475b-4b4c-b148-cf4b6ac0b719@devloop.de> (raw)
Hi all,
TIDAL is a music streaming service. As I missed a TIDAL desktop app on
gentoo I created an ebuild based on
https://github.com/Mastermindzh/tidal-hifi.
It's a node js application which drove me a bit crazy. I was today years
old when I realized that the gentoo emerge sandbox is cutting network
access :)
But the node js application, as every node js app, heavily relies on
dependencies, so I decided to go with the binary version.
Anyway, as I am not very firm with ebuilds it would be nice if someone
could do a review before I try to commit this ebuild to the official
portage via bugs.gentoo.org. Anyone? Thanks in advance.
https://source.devloop.de/damage/gentoo/src/branch/main/media-sound/tidal-hifi-bin
Stay healthy, everyone out there.
regards
Daniel
next reply other threads:[~2024-12-24 14:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-24 14:11 Daniel Buschke [this message]
2024-12-24 14:26 ` [gentoo-dev] TIDAL ebuild Filip Kobierski
2024-12-24 14:31 ` Filip Kobierski
2024-12-24 15:17 ` Lucio Sauer
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=dbcc2d0a-475b-4b4c-b148-cf4b6ac0b719@devloop.de \
--to=damage@devloop.de \
--cc=gentoo-dev@lists.gentoo.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