public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Manuel Rüger" <mrueg@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-process/tini/
Date: Mon, 14 Nov 2016 23:12:15 +0000 (UTC)	[thread overview]
Message-ID: <1479165077.3a7ac4efeac3dfd5a02032c352ddded4d5ad531c.mrueg@gentoo> (raw)

commit:     3a7ac4efeac3dfd5a02032c352ddded4d5ad531c
Author:     Manuel Rüger <mrueg <AT> gentoo <DOT> org>
AuthorDate: Mon Nov 14 23:11:17 2016 +0000
Commit:     Manuel Rüger <mrueg <AT> gentoo <DOT> org>
CommitDate: Mon Nov 14 23:11:17 2016 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=3a7ac4ef

sys-process/tini: Do not prestrip the binary

Package-Manager: portage-2.3.2

 sys-process/tini/tini-0.13.0.ebuild | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/sys-process/tini/tini-0.13.0.ebuild b/sys-process/tini/tini-0.13.0.ebuild
index 98488eb..826d432 100644
--- a/sys-process/tini/tini-0.13.0.ebuild
+++ b/sys-process/tini/tini-0.13.0.ebuild
@@ -7,7 +7,7 @@ EAPI=6
 inherit cmake-utils flag-o-matic
 
 DESCRIPTION="A tiny but valid init for containers"
-HOMEPAGE="https://github.com/krallin/${PN}"
+HOMEPAGE="https://github.com/krallin/tini"
 SRC_URI="https://github.com/krallin/${PN}/archive/v${PV}.tar.gz -> ${P}.tar.gz"
 
 LICENSE="MIT"
@@ -18,6 +18,12 @@ IUSE="+args static"
 # vim-core is needed just for the xxd program
 DEPEND="app-editors/vim-core"
 
+src_prepare() {
+	default
+	# Do not strip binary
+	sed -i -e 's/-Wl,-s")$/")/' CMakeLists.txt || die
+}
+
 src_configure() {
 	local mycmakeargs=()
 	use args || mycmakeargs+=(-DMINIMAL=ON)


             reply	other threads:[~2016-11-14 23:12 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-14 23:12 Manuel Rüger [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-12-18 10:37 [gentoo-commits] repo/gentoo:master commit in: sys-process/tini/ Sam James
2022-02-02  1:51 Sam James
2021-11-13  6:03 Sam James
2021-08-13  2:09 Yixun Lan
2021-06-15  2:06 Georgy Yakovlev
2021-06-15  2:06 Georgy Yakovlev
2021-06-11  1:00 Georgy Yakovlev
2021-05-16 12:45 Sam James
2021-04-28 16:44 Mikle Kolyada
2021-01-04 23:10 William Hubbs
2020-10-18  0:48 Georgy Yakovlev
2020-10-18  0:48 Georgy Yakovlev
2020-05-04 17:36 Thomas Deutschmann
2020-02-08 16:25 David Seifert
2020-01-17  8:52 Georgy Yakovlev
2019-11-23 11:08 Manuel Rüger
2019-04-16 17:20 Zac Medico
2019-04-16 17:18 Zac Medico
2018-12-11 10:11 Manuel Rüger
2018-07-26  7:32 Zac Medico
2018-07-26  5:45 Zac Medico
2018-06-04 19:25 Mart Raudsepp
2018-04-25  0:51 Manuel Rüger
2018-04-10  1:17 Manuel Rüger
2018-02-27 12:43 Manuel Rüger
2017-11-03 11:54 Manuel Rüger
2017-10-16  3:34 David Seifert
2017-09-25 14:07 Manuel Rüger
2017-09-10 10:59 Manuel Rüger
2017-07-05 11:24 Manuel Rüger
2017-04-22 18:53 William Hubbs
2017-04-21 19:01 William Hubbs
2017-04-21 17:52 William Hubbs
2017-04-20 22:29 Manuel Rüger
2017-04-05 10:21 Michael Weber
2017-01-03  3:09 Zac Medico
2017-01-03  2:59 Zac Medico
2016-11-14 17:49 Manuel Rüger
2016-11-14 17:43 Zac Medico
2016-11-03 19:43 Zac Medico
2016-10-13 17:18 Zac Medico
2016-10-13  1:53 Zac Medico

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=1479165077.3a7ac4efeac3dfd5a02032c352ddded4d5ad531c.mrueg@gentoo \
    --to=mrueg@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