unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Nicolas Graves via "Development of GNU Guix and the GNU System distribution." <guix-devel@gnu.org>
To: Simon Tournier <zimon.toutoune@gmail.com>, guix-devel@gnu.org
Cc: "Jean-Baptiste Volatier" <jbv@pm.me>,
	"Nicolò Balzarotti" <anothersms@gmail.com>,
	"Ludovic Courtès" <ludo@gnu.org>
Subject: Re: Follow-up on julia import script
Date: Sat, 25 Feb 2023 11:11:02 +0100	[thread overview]
Message-ID: <874jra5a2x.fsf@ngraves.fr> (raw)
In-Reply-To: <87o7pilyb4.fsf@gmail.com>


One more question ;)

On 2023-02-24 19:21, Simon Tournier wrote:

>> - Apparently Nicolo also has a similer code.
>
> I guess, it is that:
>
> https://yhetil.org/guix/8735yi9o9x.fsf@guixSD.i-did-not-set--mail-host-address--so-tickle-me

Thanks!

> Assuming some toml parser available in Guile (it is not too hard using
> PEG or a very naive approach, but still :-)), from the file
> Package.toml, you get the repository address,
>
> https://github.com/FluxML/Zygote.jl
>
> that you clone.  Then from this, you use the file Project.toml to
> consider what is inputs and what is propagated-inputs.

How would you separate inputs from propagated-inputs in this case (and
in Julia in general)?

> That’s said, another approach is to parse the JSON:
>
> https://docs.juliahub.com/Zygote/4kbLI/0.6.55/pkg.json
>
> and rely on the service JuliaHub.  This could provide some meta data
> such as synopsis, description (based on README) and license.

Oh, I didn't know about that, it might indeed be easier, since we
already have the parser, and all information at the same place.

> Cheers,
> simon

--
Best regards,
Nicolas Graves


  reply	other threads:[~2023-02-25 10:11 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. [this message]
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
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=874jra5a2x.fsf@ngraves.fr \
    --to=guix-devel@gnu.org \
    --cc=anothersms@gmail.com \
    --cc=jbv@pm.me \
    --cc=ludo@gnu.org \
    --cc=ngraves@ngraves.fr \
    --cc=zimon.toutoune@gmail.com \
    /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).