From: Simon Tournier <zimon.toutoune@gmail.com>
To: "Nicolas Graves" <ngraves@ngraves.fr>, "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org, "Jean-Baptiste Volatier" <jbv@pm.me>,
"Nicolò Balzarotti" <anothersms@gmail.com>
Subject: Re: Follow-up on julia import script
Date: Tue, 28 Feb 2023 10:25:38 +0100 [thread overview]
Message-ID: <878rgikup9.fsf@gmail.com> (raw)
In-Reply-To: <87ilfn3s42.fsf@ngraves.fr>
Hi,
On lun., 27 févr. 2023 at 19:01, Nicolas Graves via "Development of GNU Guix and the GNU System distribution." <guix-devel@gnu.org> wrote:
> That's what I meant, but it seems indeed impossible. In the hypothesis
> this juliahub script gets merged, what should we do? Really cloning the
> repository and getting it or rather just provide a given (false) hash?
Well, many importers are downloading the source for hashing it, so yes
it appears to me something the importer should do.
Moreover, cloning it would allow to extract various inputs /
propagated-inputs / native-inputs.
Thank you for pushing forward. :-)
Cheers,
simon
next prev parent reply other threads:[~2023-02-28 10:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-24 16:35 Follow-up on julia import script Nicolas Graves via Development of GNU Guix and the GNU System distribution.
2023-02-24 18:21 ` Simon Tournier
2023-02-25 10:11 ` Nicolas Graves via Development of GNU Guix and the GNU System distribution.
2023-02-25 12:19 ` Simon Tournier
2023-02-25 18:23 ` Ludovic Courtès
2023-02-27 10:14 ` Simon Tournier
2023-02-27 11:37 ` Nicolas Graves via Development of GNU Guix and the GNU System distribution.
2023-02-27 13:46 ` Simon Tournier
2023-02-27 18:01 ` Nicolas Graves via Development of GNU Guix and the GNU System distribution.
2023-02-28 9:25 ` Simon Tournier [this message]
2023-03-06 11:23 ` Nicolas Graves via Development of GNU Guix and the GNU System distribution.
2023-03-07 11:52 ` Simon Tournier
2023-03-15 12:43 ` Nicolas Graves via Development of GNU Guix and the GNU System distribution.
2023-03-18 11:17 ` Nicolas Graves via Development of GNU Guix and the GNU System distribution.
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878rgikup9.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=anothersms@gmail.com \
--cc=guix-devel@gnu.org \
--cc=jbv@pm.me \
--cc=ludo@gnu.org \
--cc=ngraves@ngraves.fr \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).