From: Lucio Sauer <watermanpaint@posteo.net>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] TIDAL ebuild
Date: Tue, 24 Dec 2024 15:17:34 +0000 [thread overview]
Message-ID: <pyf5idjltslq43tq7o55ae7b4fqscsmtqfjlbbox6aqw3dnp7a@vf4hqbn66wll> (raw)
In-Reply-To: <dbcc2d0a-475b-4b4c-b148-cf4b6ac0b719@devloop.de>
[-- Attachment #1: Type: text/plain, Size: 1126 bytes --]
On Tue, Dec 24, 2024 at 03:11:40PM +0100, Daniel Buschke wrote:
> Hi all,
Hi,
thanks for your contribution!
> 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.
>
media-sound/tidal-hifi-bin has already been packaged since last year in
the GURU overlay[1]. The linked webpage outlines how to install
packages offered in GURU and how to request access to the server to help
with development, if you're interested.
When looking to get your ebuilds reviewed, you're better off asking in
the #gentoo-dev-help channel on IRC or on the gentoo-devhelp mailing
list. Issues raised on the gentoo-dev ML generally affect a larger user
base, e.g. eclass changes, changes to global USE flags, new tools for
ebuild development.
> https://source.devloop.de/damage/gentoo/src/branch/main/media-sound/tidal-hifi-bin
>
> Stay healthy, everyone out there.
>
> regards
> Daniel
>
[1]: https://wiki.gentoo.org/wiki/Project:GURU
Best,
--
Lucio Sauer
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 618 bytes --]
prev parent reply other threads:[~2024-12-24 15:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-24 14:11 [gentoo-dev] TIDAL ebuild Daniel Buschke
2024-12-24 14:26 ` Filip Kobierski
2024-12-24 14:31 ` Filip Kobierski
2024-12-24 15:17 ` Lucio Sauer [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=pyf5idjltslq43tq7o55ae7b4fqscsmtqfjlbbox6aqw3dnp7a@vf4hqbn66wll \
--to=watermanpaint@posteo.net \
--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