From: Andreas Sturmlechner <asturm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: media-video@gentoo.org
Subject: [gentoo-dev] The state of libav stabilisation
Date: Wed, 12 Sep 2018 12:38:52 +0200 [thread overview]
Message-ID: <1676562.WTpo3CGDgJ@tuxbrain> (raw)
Is there anyone still working on libav support? It appears to me that
transition[1] and stabilisation[2] trackers are stuck for a long time without
activity. Missing libav-12 stabilisation means that in several stable
packages, USE=libav is already inaccessible without manual unmasking of the
use flag. I am not prepared to start reverting upstream commits for <libav-12
support[3].
If this is not going to change, maybe media-video/libav should be dropped to
~arch. This is still better than dropping support per-package or plastering
package.use.stable.mask with libav entries.
[1] https://bugs.gentoo.org/show_bug.cgi?id=libav-12
[2] https://bugs.gentoo.org/617508
[3] https://bugs.gentoo.org/665518
next reply other threads:[~2018-09-12 10:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-12 10:38 Andreas Sturmlechner [this message]
2018-09-13 10:44 ` [gentoo-dev] Re: The state of libav stabilisation Luca Barbato
2018-09-15 15:06 ` Andreas Sturmlechner
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=1676562.WTpo3CGDgJ@tuxbrain \
--to=asturm@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=media-video@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