From: "Michael Orlitzky" <mjo@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-php/tcpdf/
Date: Thu, 5 Jan 2017 13:51:37 +0000 (UTC) [thread overview]
Message-ID: <1483624272.9aab757628fe221db6064617c14b5d1d58f7b298.mjo@gentoo> (raw)
commit: 9aab757628fe221db6064617c14b5d1d58f7b298
Author: Michael Orlitzky <mjo <AT> gentoo <DOT> org>
AuthorDate: Thu Jan 5 13:43:34 2017 +0000
Commit: Michael Orlitzky <mjo <AT> gentoo <DOT> org>
CommitDate: Thu Jan 5 13:51:12 2017 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=9aab7576
dev-php/tcpdf: new revision fixing the location of tcpdf_addfont.php.
The result of an "insinto" followed by a "doexe" is... not as
intended. This new revision changes the "insinto" into a "exeinto" so
that tcpdf_addfont.php is not installed to the root.
Package-Manager: portage-2.3.0
dev-php/tcpdf/{tcpdf-6.2.13.ebuild => tcpdf-6.2.13-r1.ebuild} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-php/tcpdf/tcpdf-6.2.13.ebuild b/dev-php/tcpdf/tcpdf-6.2.13-r1.ebuild
similarity index 96%
rename from dev-php/tcpdf/tcpdf-6.2.13.ebuild
rename to dev-php/tcpdf/tcpdf-6.2.13-r1.ebuild
index 1c1012d..018dcea 100644
--- a/dev-php/tcpdf/tcpdf-6.2.13.ebuild
+++ b/dev-php/tcpdf/tcpdf-6.2.13-r1.ebuild
@@ -25,7 +25,7 @@ src_install() {
# look for it in its own source tree (not in /etc where we've put it).
dosym /etc/tcpdf_config.php "/usr/share/php/${PN}/config/tcpdf_config.php"
- insinto "/usr/share/php/${PN}/tools"
+ exeinto "/usr/share/php/${PN}/tools"
doexe tools/tcpdf_addfont.php
insinto "/usr/share/php/${PN}"
next reply other threads:[~2017-01-05 13:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-05 13:51 Michael Orlitzky [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-03-14 6:35 [gentoo-commits] repo/gentoo:master commit in: dev-php/tcpdf/ Sam James
2019-02-22 18:29 Thomas Deutschmann
2018-10-31 13:15 Brian Evans
2018-10-31 13:15 Brian Evans
2018-02-20 19:30 Brian Evans
2018-02-20 19:30 Brian Evans
2017-01-05 0:51 Michael Orlitzky
2017-01-05 0:51 Michael Orlitzky
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=1483624272.9aab757628fe221db6064617c14b5d1d58f7b298.mjo@gentoo \
--to=mjo@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