public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Maciej Barć" <xgqt@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-lang/boogie/
Date: Sun, 17 Sep 2023 22:37:24 +0000 (UTC)	[thread overview]
Message-ID: <1694990241.735fa9cf30b911363a9e63d8900bdd63e2e7ca01.xgqt@gentoo> (raw)

commit:     735fa9cf30b911363a9e63d8900bdd63e2e7ca01
Author:     Maciej Barć <xgqt <AT> gentoo <DOT> org>
AuthorDate: Sun Sep 17 22:36:16 2023 +0000
Commit:     Maciej Barć <xgqt <AT> gentoo <DOT> org>
CommitDate: Sun Sep 17 22:37:21 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=735fa9cf

dev-lang/boogie: add missing src_unpack to support git

Signed-off-by: Maciej Barć <xgqt <AT> gentoo.org>

 dev-lang/boogie/boogie-3.0.4.ebuild | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/dev-lang/boogie/boogie-3.0.4.ebuild b/dev-lang/boogie/boogie-3.0.4.ebuild
index 99ebc26b59b9..4a65a8887995 100644
--- a/dev-lang/boogie/boogie-3.0.4.ebuild
+++ b/dev-lang/boogie/boogie-3.0.4.ebuild
@@ -238,6 +238,14 @@ pkg_setup() {
 	dotnet-pkg_pkg_setup
 }
 
+src_unpack() {
+	dotnet-pkg_src_unpack
+
+	if [[ -n ${EGIT_REPO_URI} ]] ; then
+		git-r3_src_unpack
+	fi
+}
+
 src_prepare() {
 	# Bump used .NET version: 6.0 -> 7.0
 	sed -e "s|net6.0|net7.0|g" \


             reply	other threads:[~2023-09-17 22:37 UTC|newest]

Thread overview: 79+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-17 22:37 Maciej Barć [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-12-28 16:01 [gentoo-commits] repo/gentoo:master commit in: dev-lang/boogie/ Sam James
2024-11-14 23:40 Maciej Barć
2024-10-25 18:52 Maciej Barć
2024-10-25 18:52 Maciej Barć
2024-10-23 17:03 Sam James
2024-10-23 15:44 Maciej Barć
2024-10-23 15:44 Maciej Barć
2024-10-15 14:30 Maciej Barć
2024-10-13 19:23 Maciej Barć
2024-10-08 23:07 Maciej Barć
2024-10-08 23:07 Maciej Barć
2024-09-27  5:30 Arthur Zamarin
2024-09-12 12:08 Maciej Barć
2024-09-12 12:08 Maciej Barć
2024-09-12 12:08 Maciej Barć
2024-09-03 18:32 Jakov Smolić
2024-08-24 13:12 Michał Górny
2024-08-16 16:21 Maciej Barć
2024-08-16 16:21 Maciej Barć
2024-08-10 18:55 Arthur Zamarin
2024-07-31  0:03 Maciej Barć
2024-07-19 11:02 Maciej Barć
2024-07-04 12:44 Maciej Barć
2024-06-27 22:42 Maciej Barć
2024-06-25 22:03 Sam James
2024-05-23 22:08 Maciej Barć
2024-05-23 22:08 Maciej Barć
2024-05-23 22:08 Maciej Barć
2024-05-18  3:19 Sam James
2024-04-24 17:10 Maciej Barć
2024-04-24 17:10 Maciej Barć
2024-04-17 23:11 Sam James
2024-04-13 22:56 Maciej Barć
2024-04-13 22:56 Maciej Barć
2024-04-13 22:56 Maciej Barć
2024-04-13 22:56 Maciej Barć
2024-04-11  4:55 Arthur Zamarin
2024-03-13 16:40 Maciej Barć
2024-03-10  0:29 Maciej Barć
2024-03-08 22:18 Maciej Barć
2024-03-08 22:18 Maciej Barć
2024-03-08 13:09 Arthur Zamarin
2024-03-05 18:46 Maciej Barć
2024-03-05 18:46 Maciej Barć
2024-03-04 21:58 Maciej Barć
2024-03-04 21:58 Maciej Barć
2024-02-27 23:57 Sam James
2024-02-19 20:54 Maciej Barć
2024-02-10 16:24 Maciej Barć
2024-02-03  8:22 Arthur Zamarin
2024-02-02 23:06 Maciej Barć
2024-02-02 23:06 Maciej Barć
2024-01-27 20:06 Ionen Wolkens
2024-01-22 22:19 Maciej Barć
2024-01-12 23:22 Maciej Barć
2023-12-27 23:44 Maciej Barć
2023-12-27 23:44 Maciej Barć
2023-12-08  8:31 Maciej Barć
2023-12-08  8:31 Maciej Barć
2023-11-29 19:31 Maciej Barć
2023-11-21 18:37 Maciej Barć
2023-11-16 23:38 Maciej Barć
2023-11-16 23:38 Maciej Barć
2023-11-13 22:04 Sam James
2023-10-11  0:19 Maciej Barć
2023-10-07 22:39 Maciej Barć
2023-09-16 14:48 Maciej Barć
2023-09-15 20:49 Maciej Barć
2023-06-19 18:29 Maciej Barć
2023-06-19 18:29 Maciej Barć
2023-02-28 18:03 Maciej Barć
2022-11-28 20:33 Maciej Barć
2022-11-18  0:53 Maciej Barć
2022-10-06 20:56 Maciej Barć
2022-10-06 14:27 Maciej Barć
2022-10-04 15:24 Maciej Barć
2022-10-04  1:50 Maciej Barć
2022-10-03 21:38 Maciej Barć

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=1694990241.735fa9cf30b911363a9e63d8900bdd63e2e7ca01.xgqt@gentoo \
    --to=xgqt@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