From: "Alexis Ballier" <aballier@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: media-libs/libogg/
Date: Mon, 8 Jan 2018 08:08:53 +0000 (UTC) [thread overview]
Message-ID: <1515398900.84c29736fc5fbe494bd356a053f192e712cb72a2.aballier@gentoo> (raw)
commit: 84c29736fc5fbe494bd356a053f192e712cb72a2
Author: Marty E. Plummer <hanetzer <AT> protonmail <DOT> com>
AuthorDate: Mon Jan 8 03:21:15 2018 +0000
Commit: Alexis Ballier <aballier <AT> gentoo <DOT> org>
CommitDate: Mon Jan 8 08:08:20 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=84c29736
media-libs/libogg: find and remove '*.a' not required
Not sure if this was changed in a previous version of libogg, but
libogg-1.3.3 correctly respects --enable-static/--disable-static, and
does not produce a static library when built with USE=-static-libs.
The find "${ED}" -name '*.a' -delete || die line also kills off
libogg.dll.a, which is needed for shared linking on mingw-w64, so
it should be removed as uneeded and harmful.
Package-Manager: Portage-2.3.19, Repoman-2.3.6
Signed-off-by: Marty E. Plummer <hanetzer <AT> protonmail.com>
media-libs/libogg/libogg-1.3.3.ebuild | 5 +----
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/media-libs/libogg/libogg-1.3.3.ebuild b/media-libs/libogg/libogg-1.3.3.ebuild
index 27c0175879b..db5bd9b334d 100644
--- a/media-libs/libogg/libogg-1.3.3.ebuild
+++ b/media-libs/libogg/libogg-1.3.3.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2017 Gentoo Foundation
+# Copyright 1999-2018 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
EAPI=6
@@ -30,7 +30,4 @@ multilib_src_configure() {
multilib_src_install_all() {
einstalldocs
find "${ED}" -name "*.la" -delete || die
- if ! use static-libs ; then
- find "${ED}" -name "*.a" -delete || die
- fi
}
next reply other threads:[~2018-01-08 8:08 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-08 8:08 Alexis Ballier [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-05-17 7:56 [gentoo-commits] repo/gentoo:master commit in: media-libs/libogg/ WANG Xuerui
2022-04-26 2:39 Sam James
2021-10-03 13:47 James Le Cuirot
2021-07-13 4:29 Miroslav Šulc
2021-07-13 4:02 Sam James
2021-07-07 6:31 Agostino Sarubbo
2021-07-07 6:30 Agostino Sarubbo
2021-07-07 2:17 Sam James
2021-07-06 18:02 Sam James
2021-07-06 17:59 Sam James
2021-06-04 18:21 Sam James
2021-05-28 15:37 David Seifert
2021-05-25 8:25 Yixun Lan
2020-09-08 7:48 Miroslav Šulc
2020-09-04 23:52 Sam James
2020-09-04 10:31 Sergei Trofimovich
2020-09-04 0:23 Sam James
2020-09-04 0:21 Sam James
2020-09-03 14:29 Thomas Deutschmann
2019-09-05 14:27 Lars Wendler
2019-05-11 1:43 Aaron Bauman
2018-06-11 0:04 Andreas Sturmlechner
2018-04-01 22:16 Sergei Trofimovich
2018-03-15 16:32 Mikle Kolyada
2018-03-05 14:52 Tobias Klausmann
2018-02-22 7:55 Sergei Trofimovich
2018-02-21 22:42 Sergei Trofimovich
2018-02-21 7:42 Sergei Trofimovich
2018-02-19 16:57 Thomas Deutschmann
2018-02-19 7:31 Sergei Trofimovich
2017-11-10 11:18 Lars Wendler
2017-08-31 12:58 Tim Harder
2017-04-12 11:10 Tim Harder
2017-01-29 19:15 Fabian Groffen
2017-01-15 20:27 Markus Meier
2017-01-14 11:44 Jeroen Roovers
2017-01-02 9:54 Agostino Sarubbo
2016-12-18 1:58 Aaron Bauman
2016-12-06 9:04 Tobias Klausmann
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=1515398900.84c29736fc5fbe494bd356a053f192e712cb72a2.aballier@gentoo \
--to=aballier@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