From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] data/gentoo-news:master commit in: 2015-02-01-use-libav/
Date: Mon, 6 Apr 2020 04:58:58 +0000 (UTC) [thread overview]
Message-ID: <1586149074.fa17171db0d7284aa55c2ed592922483d1bfadd8.mgorny@gentoo> (raw)
commit: fa17171db0d7284aa55c2ed592922483d1bfadd8
Author: Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Mon Apr 6 04:57:44 2020 +0000
Commit: Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Mon Apr 6 04:57:54 2020 +0000
URL: https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=fa17171d
Remove libav news item since the package was last rited
Signed-off-by: Michał Górny <mgorny <AT> gentoo.org>
2015-02-01-use-libav/2015-02-01-use-libav.en.txt | 35 ------------------------
1 file changed, 35 deletions(-)
diff --git a/2015-02-01-use-libav/2015-02-01-use-libav.en.txt b/2015-02-01-use-libav/2015-02-01-use-libav.en.txt
deleted file mode 100644
index 47d54f4..0000000
--- a/2015-02-01-use-libav/2015-02-01-use-libav.en.txt
+++ /dev/null
@@ -1,35 +0,0 @@
-Title: ffmpeg/libav conflict management: USE=libav
-Author: Michał Górny <mgorny@gentoo.org>
-Content-Type: text/plain
-Posted: 2015-02-01
-Revision: 2
-News-Item-Format: 1.0
-Display-If-Installed: media-video/ffmpeg
-Display-If-Installed: media-video/libav
-
-The support for automatic choice between ffmpeg and libav is going to be
-deprecated in favor of explicit choice via USE flags. This change aims
-to solve multiple repeating issues, including Portage undesirably
-wanting to replace one package with the other, lack of proper reverse
-dependency on ffmpeg/libav upgrades and some of the hard-to-understand
-upgrade failures involving blockers. It also may be used to make ffmpeg
-and libav co-installable in the future.
-
-The current USE=ffmpeg will maintain its role of enabling optional
-support for ffmpeg or a compatible implementation (libav) in a package.
-However, whenever appropriate additional USE=libav will be introduced to
-control the preference of one implementation over the other.
-
-Users who currently use libav need to enable USE=libav in
-/etc/portage/make.conf. It should be noted that users still need to
-enable USE=ffmpeg on packages with optional libav support as well.
-Users who currently use ffmpeg need to take no action.
-
-Please also note that some packages support only one of the two
-implementations. An attempt to install one of those packages may result
-in blockers requiring the user changes the global USE=libav state.
-
-Please do not alter the state of 'libav' flag on a per-package basis
-(e.g. via package.use). The flag needs to be set globally to have
-consistent value throughout all packages. Otherwise, blockers will
-prevent upgrades.
reply other threads:[~2020-04-06 4:59 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1586149074.fa17171db0d7284aa55c2ed592922483d1bfadd8.mgorny@gentoo \
--to=mgorny@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--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