unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
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, 07 Mar 2023 12:52:28 +0100	[thread overview]
Message-ID: <86cz5kdbib.fsf@gmail.com> (raw)
In-Reply-To: <87edq2dsy7.fsf@ngraves.fr>

Hi Nicolas,

On Mon, 06 Mar 2023 at 12:23, Nicolas Graves wrote:

> I have a WIP version which should solve the issues of hash and
> native-inputs.

Awesome!


> I still have the two following issues, if someone has a hint:
>
>> - there's a difficulty for defining guix-name->julia-name with the
>>   simple guix/import/utils.scm snake-case. We should define proper
>>   functions to convert without ambiguity from CamelCase to snake-case
>>   and back, and that also encompasses cases like JuMP and OCReract. I
>>   had one option in mind but haven't tested it to get the name in the
>>   url. Or maybe we should have a #:julia-name field in arguments or
>>   properties. WDYT ?

I suggest to track the upstream name with the field ’properties’, e.g.,

    (properties `((upstream-name . "CamelCase")))

as it is done for CRAN/Bioconductor importer; see (guix import cran).


>> - readme is full of html junk, I don't know if we can process it to get
>>   pure text output easily in Guile ?

Yeah, I do not know either.

Cheers,
simon


  reply	other threads:[~2023-03-07 13:48 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
2023-03-06 11:23             ` Nicolas Graves via Development of GNU Guix and the GNU System distribution.
2023-03-07 11:52               ` Simon Tournier [this message]
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=86cz5kdbib.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).