unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Martin Becze <mjbecze@riseup.net>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: guix-devel@gnu.org
Subject: Re: dependancies for importers
Date: Thu, 5 Sep 2019 15:18:02 +0200	[thread overview]
Message-ID: <33c29506-1fa1-1ced-7e4d-0d53de3df6fc@riseup.net> (raw)
In-Reply-To: <20190905121442.GW13917@E5400>


[-- Attachment #1.1: Type: text/plain, Size: 1162 bytes --]


On 9/5/19 2:14 PM, Efraim Flashner wrote:
> 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.
>
yes I already did this. But it doesn't work to well if it can't also get
the correct version for the dependencies.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      reply	other threads:[~2019-09-05 13:18 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
2019-09-05 13:18   ` Martin Becze [this message]

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=33c29506-1fa1-1ced-7e4d-0d53de3df6fc@riseup.net \
    --to=mjbecze@riseup.net \
    --cc=efraim@flashner.co.il \
    --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).