unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: Guix-devel <guix-devel@gnu.org>
Subject: Anybody please help improving rust crates importer
Date: Sat, 7 Nov 2020 19:08:51 +0100	[thread overview]
Message-ID: <365d7bce-f986-ba52-26e2-9e75233b363f@crazy-compilers.com> (raw)

Hi,

can anybody please help improving the crates importer? My guile skills
are far to poor and my time is to limited. Help is appreciated!

Why the crates importer needs to be improved

rust is still an young language and many rust packages (crates) still
have 0.x versions. Also crates use semantic versioning and describe
dependencies the same way. Thus, when importing or updating a package,
the packager has to validate *every* dependency manually.

To give you a number: When updating seqouia-pgp, one new dependency was
added, which introduced 151 dependencies - each of which need to be
checked and adopted *manually*.

How the crates importer needs to be improved

  *

    Automatically add the semantic version base to the package's
    variable name (e.g. rust-aaa-1, rust-aaa-0.7). This is stupid work,
    currently to be done manually. Anyhow, this should be easy to implement.

  *

    When creating the package sexp, refer to each dependency using its
    semantic versioned variable name. This is stupid work, currently to
    be done manually. Anyhow, this should be easy to implement, once the
    next point is done.

  *

    When looking up dependencies, follow the semantic version
    requirement. Looking this up manually is the most elaborate, stupid
    work - and it is demotivating.

  *

    When checking whether a dependency is already packaged, take the
    semantic version into account. This is another demotivating,
    elaborate work, done by the computer much faster ans less error-prone.

Anybody taking up this job? I can provide more details, e.g. links, API
end-points, etc.

(Side-note: I'm not a rust developer, I'm just trying to make
sequoia-pgp and pEp available for guix.)

-- 
Regards
Hartmut Goebel

| Hartmut Goebel          | h.goebel@crazy-compilers.com               |
| www.crazy-compilers.com | compilers which you thought are impossible |



             reply	other threads:[~2020-11-07 18:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-07 18:08 Hartmut Goebel [this message]
2020-11-07 18:13 ` Anybody please help improving rust crates importer John Soo

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=365d7bce-f986-ba52-26e2-9e75233b363f@crazy-compilers.com \
    --to=h.goebel@crazy-compilers.com \
    --cc=guix-devel@gnu.org \
    /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).