Re: Follow-up on julia import script

[Ludovic Courtès]

Hi,

Simon Tournier <zimon.touto...@gmail.com> skribis:

> For instance, consider the package julia-tables, it reads:
>
>     (propagated-inputs
>      (list julia-dataapi
>            julia-datavalueinterfaces
>            julia-iteratorinterfaceextensions
>            julia-tabletraits))
>     (native-inputs
>      (list julia-datavalues
>            julia-queryoperators))
>
> when Project.toml reads
>
> [deps]
> DataAPI = "9a962f9c-6df0-11e9-0e5d-c546b8b5ee8a"
> DataValueInterfaces = "e2d170a0-9d28-54be-80f0-106bbe20a464"
> IteratorInterfaceExtensions = "82899510-4779-5014-852e-03e436cf321d"
> LinearAlgebra = "37e2e46d-f89d-539d-b4ee-838fcccc9c8e"
> OrderedCollections = "bac558e1-5e72-5ebc-8fee-abe8a469f55d"
> TableTraits = "3783bdb8-4a98-5b6b-af9a-565f29a5fe9c"
> Test = "8dfed614-e22c-5e08-85e1-65c5234f0b40"

How does one resolve those UUIDs?

It seems that one would “just” need a toml parser to put this to work?

The other option you mentioned—using the JuliaHub API—doesn’t sound too
bad to me, and it would be quite easy to implement, similar to (guix
import pypi) and the like I suppose?

Curiously,
Ludo’.