all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: Martin Becze <mjbecze@riseup.net>
Cc: guix-devel@gnu.org
Subject: Re: dependancies for importers
Date: Thu, 5 Sep 2019 15:14:42 +0300	[thread overview]
Message-ID: <20190905121442.GW13917@E5400> (raw)
In-Reply-To: <fa4323d0598813c4fa8aff6ac4e43e21@riseup.net>

[-- Attachment #1: Type: text/plain, Size: 1188 bytes --]

On Wed, Sep 04, 2019 at 04:20:46AM -0700, Martin Becze wrote:
> Hello,
> I'm wokring on the crate importer. It currently doesn't support
> versioning of dependancies and just always uses the latest version of a
> given crate. Of course this would break main rust packages, so i'm
> trying to add version support. To do this I need to be able it find a
> dependancy in a specified semantic version range and to do this I'm
> attempting to use a guile module
> (https://ngyro.com/software/guile-semver/). Is it possible to package
> this module then use it in an importer? Or should I just put the modules
> code directly in the `guix/import` ?
> 

Although not actually answering your question, what about modifying the
crate importer to allow for getting a specific version? For example
'guix import crate addr2line/0.9' or '/0.9.0'. I think it works with the
pypi importer, but I haven't inspected the code to see if that's on
purpose or a happy accident.

-- 
Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2019-09-05 12:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-04 11:20 dependancies for importers Martin Becze
2019-09-05 12:14 ` Efraim Flashner [this message]
2019-09-05 13:18   ` Martin Becze

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190905121442.GW13917@E5400 \
    --to=efraim@flashner.co.il \
    --cc=guix-devel@gnu.org \
    --cc=mjbecze@riseup.net \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.