From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: media-tv/gentoo-vdr-scripts/
Date: Thu, 5 May 2016 21:14:52 +0000 (UTC) [thread overview]
Message-ID: <1462482886.41f47516b7fb6ea09963717f0f4cb49e2ce14787.mgorny@gentoo> (raw)
commit: 41f47516b7fb6ea09963717f0f4cb49e2ce14787
Author: Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Thu May 5 21:13:12 2016 +0000
Commit: Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Thu May 5 21:14:46 2016 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=41f47516
media-tv/gentoo-vdr-scripts: Fix DOCS expansion
Delay DOCS expansion until src_install(). It is meaningless in global
scope since it happens in arbitrary directory which will not have
README* files. Furthermore, it triggers verbose failure due to failglob.
media-tv/gentoo-vdr-scripts/gentoo-vdr-scripts-2.7.5.ebuild | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/media-tv/gentoo-vdr-scripts/gentoo-vdr-scripts-2.7.5.ebuild b/media-tv/gentoo-vdr-scripts/gentoo-vdr-scripts-2.7.5.ebuild
index 4e8431b..ba4f064 100644
--- a/media-tv/gentoo-vdr-scripts/gentoo-vdr-scripts-2.7.5.ebuild
+++ b/media-tv/gentoo-vdr-scripts/gentoo-vdr-scripts-2.7.5.ebuild
@@ -22,8 +22,6 @@ RDEPEND="nvram? ( sys-power/nvram-wakeup )
VDR_HOME=/var/vdr
-DOCS=( README* TODO ChangeLog )
-
pkg_setup() {
enewgroup vdr
@@ -43,6 +41,8 @@ src_prepare() {
}
src_install() {
+ local DOCS=( README* TODO ChangeLog )
+
default
# create necessary directories
next reply other threads:[~2016-05-05 21:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-05 21:14 Michał Górny [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-03-17 13:33 [gentoo-commits] repo/gentoo:master commit in: media-tv/gentoo-vdr-scripts/ Joonas Niilola
2022-03-17 13:33 Joonas Niilola
2022-02-13 21:34 Conrad Kostecki
2020-02-24 12:23 Jörg Bornkessel
2020-02-04 19:45 Jörg Bornkessel
2020-01-28 7:39 Agostino Sarubbo
2020-01-27 15:44 Thomas Deutschmann
2020-01-12 18:38 Jörg Bornkessel
2019-12-15 15:23 Joerg Bornkessel
2019-12-15 1:06 Joerg Bornkessel
2017-11-26 23:11 David Seifert
2016-06-19 12:24 Joerg Bornkessel
2016-06-12 18:45 Joerg Bornkessel
2016-05-15 23:32 Joerg Bornkessel
2016-05-03 16:29 Joerg Bornkessel
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=1462482886.41f47516b7fb6ea09963717f0f4cb49e2ce14787.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