[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Follow-up on julia import script
From: |
Nicolas Graves |
Subject: |
Follow-up on julia import script |
Date: |
Fri, 24 Feb 2023 17:35:00 +0100 |
Hi all,
I asked a few questions today on the IRC channel about a julia import
script.
Just to summarize and be able to follow the subject later:
- I was looking for a way to write a julia import script base on
information in julia general package repository, which can be quite
simple if we have a functional guile toml/ini parser included (I
couldn't get my parser to work properly, but that might be fixable).
- jvb shared his julia importer code here : https://gitlab.com/vjb/guix.jl
- Apparently Nicolo also has a similer code.
- jvb and zimoun defended that the Julia ecosystem evolves so quickly
that writing a manual functional julia import script might be
difficult to maintain, in particular because Julia uses an advanced
resolver for its compatibilities.
- My approach was a bit different but indeed didn't have the ambition to
resolve compatibilities between packages (I need to check that but the
check or the build phase should fail it packages are incompatible,
thus when trying to build the imported package, we should now which
packages should be updated if necessary). If we only restrain imports
to the general package repository, then the task becomes much more
simple :
- from the package name, you can generate the uri of the following
files
- parse Project.toml to get source information
- parse Versions.toml to get source hash information
- parse Deps.toml to get information about dependencies
Well there is no package description or such, but I think it makes a
decent start for writing package information. These are all unnested
toml/ini files, so if we manage to parse them with a simple function,
I guess we could have such a small / limited importer.
I do have the very beginning of a script here, but couldn't finish the
parser :
https://paste.sr.ht/~ngraves/bbeb74a720e717319344ee3c3e6ea477b378068f/manage
- Maybe we could combine both by
- using this limited importer if julia is not in the PATH
- using a proper guix.jl importer if julia and the importer are present in
the PATH
or something like that ?
I do not have a strong opinion about which option is more suitable, but
would greatly profit from having a functional and supported julia import
script. Sorry for inaccuracies if there are some, I do this from memory
mostly.
--
Best regards,
Nicolas Graves
- Follow-up on julia import script,
Nicolas Graves <=
- Re: Follow-up on julia import script, Simon Tournier, 2023/02/24
- Re: Follow-up on julia import script, Nicolas Graves, 2023/02/25
- Re: Follow-up on julia import script, Simon Tournier, 2023/02/25
- Re: Follow-up on julia import script, Ludovic Courtès, 2023/02/25
- Re: Follow-up on julia import script, Simon Tournier, 2023/02/27
- Re: Follow-up on julia import script, Nicolas Graves, 2023/02/27
- Re: Follow-up on julia import script, Simon Tournier, 2023/02/27
- Re: Follow-up on julia import script, Nicolas Graves, 2023/02/27
- Re: Follow-up on julia import script, Simon Tournier, 2023/02/28