public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Lucio Sauer" <watermanpaint@posteo.net>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:dev commit in: dev-vcs/pijul/
Date: Tue, 10 Sep 2024 19:49:50 +0000 (UTC)	[thread overview]
Message-ID: <1725997393.74799873b54e9345e02be6998000845eb077a46b.watermanpaint@gentoo> (raw)

commit:     74799873b54e9345e02be6998000845eb077a46b
Author:     Lucio Sauer <watermanpaint <AT> posteo <DOT> net>
AuthorDate: Tue Sep 10 19:43:13 2024 +0000
Commit:     Lucio Sauer <watermanpaint <AT> posteo <DOT> net>
CommitDate: Tue Sep 10 19:43:13 2024 +0000
URL:        https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=74799873

dev-vcs/pijul: speed up SRC_URI generation for Cargo crates

fix variable order

Signed-off-by: Lucio Sauer <watermanpaint <AT> posteo.net>

 dev-vcs/pijul/pijul-1.0.0_beta9.ebuild | 15 +++++++--------
 1 file changed, 7 insertions(+), 8 deletions(-)

diff --git a/dev-vcs/pijul/pijul-1.0.0_beta9.ebuild b/dev-vcs/pijul/pijul-1.0.0_beta9.ebuild
index 9c34d5953..42aa036fb 100644
--- a/dev-vcs/pijul/pijul-1.0.0_beta9.ebuild
+++ b/dev-vcs/pijul/pijul-1.0.0_beta9.ebuild
@@ -439,20 +439,19 @@ inherit cargo
 
 DESCRIPTION="A distributed version control system based on a theory of patches"
 HOMEPAGE="https://pijul.org/ https://nest.pijul.com/pijul/pijul"
-SRC_URI="
-	$(cargo_crate_uris)
-"
+SRC_URI="${CARGO_CRATE_URIS}"
+
+# We get the sources from one of the crates, as the Pijul source is
+# managed with Pijul on nest.pijul.com - we obviously can't clone it
+# (because we'd need a working pijul binary to do that), and the Nest
+# doesn't support exporting archives (yet).
+S="${ECARGO_VENDOR}/${PN}-${MY_PIJUL_PV}"
 
 LICENSE="GPL-2+"
 # Dependent crate licenses
 LICENSE+=" Apache-2.0 BSD-2 BSD CC0-1.0 MIT Unicode-DFS-2016 ZLIB"
 SLOT="0"
 KEYWORDS="~amd64"
-# We get the sources from one of the crates, as the Pijul source is
-# managed with Pijul on nest.pijul.com - we obviously can't clone it
-# (because we'd need a working pijul binary to do that), and the Nest
-# doesn't support exporting archives (yet).
-S="${WORKDIR}/cargo_home/gentoo/${PN}-${MY_PIJUL_PV}"
 IUSE="git"
 
 DEPEND="


             reply	other threads:[~2024-09-10 19:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-10 19:49 Lucio Sauer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-09-10 19:49 [gentoo-commits] repo/proj/guru:dev commit in: dev-vcs/pijul/ Lucio Sauer
2024-09-07  5:39 Thomas Bracht Laumann Jespersen
2024-09-05  4:54 Thomas Bracht Laumann Jespersen

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=1725997393.74799873b54e9345e02be6998000845eb077a46b.watermanpaint@gentoo \
    --to=watermanpaint@posteo.net \
    --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