public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Justin Lecher" <jlec@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sci-visualization/veusz/
Date: Mon, 23 Nov 2015 10:05:45 +0000 (UTC)	[thread overview]
Message-ID: <1448273131.f592cd94e57c175c4f8f501d87658ce9a8b81df8.jlec@gentoo> (raw)

commit:     f592cd94e57c175c4f8f501d87658ce9a8b81df8
Author:     Justin Lecher <jlec <AT> gentoo <DOT> org>
AuthorDate: Mon Nov 23 08:59:17 2015 +0000
Commit:     Justin Lecher <jlec <AT> gentoo <DOT> org>
CommitDate: Mon Nov 23 10:05:31 2015 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f592cd94

sci-visualization/veusz: Drop symlink into PORTDIR

Gentoo-Bug: https://bugs.gentoo.org/show_bug.cgi?id=341653

Package-Manager: portage-2.2.25
Signed-off-by: Justin Lecher <jlec <AT> gentoo.org>

 sci-visualization/veusz/veusz-1.23.ebuild | 10 ++++++++--
 1 file changed, 8 insertions(+), 2 deletions(-)

diff --git a/sci-visualization/veusz/veusz-1.23.ebuild b/sci-visualization/veusz/veusz-1.23.ebuild
index 42bfe9d..ebe7f7c 100644
--- a/sci-visualization/veusz/veusz-1.23.ebuild
+++ b/sci-visualization/veusz/veusz-1.23.ebuild
@@ -48,8 +48,14 @@ python_install() {
 	distutils-r1_python_install
 	# symlink the license, bug #341653
 	rm "${D}/$(python_get_sitedir)"/${PN}/{COPYING,AUTHORS,ChangeLog} || die
-	ln -s "${PORTDIR}"/licenses/${LICENSE} \
-		"${D}/$(python_get_sitedir)"/${PN}/COPYING || die
+	mkdir -p "${D}/$(python_get_sitedir)" || die
+	cat >> "${D}/$(python_get_sitedir)"/${PN}/COPYING <<- EOF
+	Please visit
+
+	https://www.gnu.org/licenses/gpl-2.0.html
+
+	for the full license text.
+	EOF
 }
 
 python_install_all() {


             reply	other threads:[~2015-11-23 10:05 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-23 10:05 Justin Lecher [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-06-04  9:45 [gentoo-commits] repo/gentoo:master commit in: sci-visualization/veusz/ Andrey Grozin
2025-05-05 13:51 Andrey Grozin
2025-04-30  5:44 Andrey Grozin
2024-11-23 17:31 Andreas Sturmlechner
2024-04-18  9:54 Andrey Grozin
2024-04-18  9:40 Andrey Grozin
2023-04-12 15:18 Andrey Grozin
2023-02-16  6:35 Andrey Grozin
2023-02-16  6:34 Andrey Grozin
2022-10-06 10:08 Andrew Ammerlaan
2021-10-06  8:33 Jakov Smolić
2021-06-02  7:38 Andrew Ammerlaan
2021-05-06 10:43 Andrey Grozin
2021-01-08  0:00 Andreas Sturmlechner
2021-01-01  1:56 Michał Górny
2020-10-14 10:43 Alexey Shvetsov
2020-03-17 15:17 Andrey Grozin
2020-02-09 10:09 Andrey Grozin
2019-12-04 17:15 Michał Górny
2019-11-10 15:27 Michał Górny
2019-11-10 10:34 Andrey Grozin
2018-08-08 13:23 Andrey Grozin
2018-06-13  8:52 Andrey Grozin
2018-04-22 20:51 Andrey Grozin
2018-01-14 16:09 Andreas Sturmlechner
2018-01-04 15:46 Andrey Grozin
2017-07-26 15:14 Andrey Grozin
2017-03-18  7:33 Michał Górny
2017-01-11 16:17 Agostino Sarubbo
2017-01-01 14:20 Michael Palimaka
2016-12-31  6:08 Andrey Grozin
2016-07-31 15:55 David Seifert
2016-06-09 20:01 Sebastien Fabbro
2016-05-08 11:19 Andrey Grozin
2016-03-04 13:33 Andrey Grozin
2016-03-02  7:44 Andrey Grozin
2015-10-22  8:32 Justin Lecher
2015-10-22  8:32 Justin Lecher
2015-10-22  8:32 Justin Lecher

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=1448273131.f592cd94e57c175c4f8f501d87658ce9a8b81df8.jlec@gentoo \
    --to=jlec@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