From: Arve Barsnes <arve.barsnes@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] Unmessing mod/tracker music file flags (mikmod, modplug, openmpt)
Date: Wed, 11 Dec 2024 12:31:38 +0100 [thread overview]
Message-ID: <CAJjrzcVo73d3N5RQu3Q1b-sFPveBS7W-GO7kPf2aOmKMhSAOtQ@mail.gmail.com> (raw)
In-Reply-To: <e0e9c7710a1b2e66a53ba64f369cd60ab111cd90.camel@gentoo.org>
On Wed, 11 Dec 2024 at 11:20, Michał Górny <mgorny@gentoo.org> wrote:
> Right now we have three flags that do pretty much the same thing, via
> different libraries:
>
> Given that they are roughly used in the same way, and only a small
> subset of packages (e.g. mpv) support more than one library, how about
> settling on a single feature flag instead? While they probably differ
> in fine details like the exact list of supported file formats,
> the overlap is wide enough to justify it.
>
> Such as:
>
> mod - Enable support for a variety of tracker module (.it, .mod, .s3m, .xm, and more) music files
As a user of these things, I'm all for it. Makes it easy to know what
to enable when I want it on a package.
Regards,
Arve
next prev parent reply other threads:[~2024-12-11 11:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 10:20 [gentoo-dev] [RFC] Unmessing mod/tracker music file flags (mikmod, modplug, openmpt) Michał Górny
2024-12-11 11:31 ` Arve Barsnes [this message]
2024-12-12 21:56 ` James Le Cuirot
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=CAJjrzcVo73d3N5RQu3Q1b-sFPveBS7W-GO7kPf2aOmKMhSAOtQ@mail.gmail.com \
--to=arve.barsnes@gmail.com \
--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