unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: phodina <phodina@protonmail.com>
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Crates versions and their replacement
Date: Sun, 10 Oct 2021 07:11:57 +0000	[thread overview]
Message-ID: <ebVG5JKeqV2z0xvaz9mWlVuWOdy6FMZtrNeCJ30MoO7RwQuMOm0lw27gJ7JmHKV7fOE6vPdKM4bZsZtAbjMWTftJMtn8RL5LqXAGF6IvPZQ=@protonmail.com> (raw)
In-Reply-To: <50766b90-5f3d-bb9d-c72f-367699e36b1a@crazy-compilers.com>

Hi Hartmut,

On Tuesday, October 5th, 2021 at 8:19 PM, Hartmut Goebel <h.goebel@crazy-compilers.com> wrote:

> Am 03.10.21 um 09:02 schrieb phodina:
>
> > Now comes the question. How often should it be use and what are the
> >
> > pros and cons?
>
> I suggest to use this only if required, since versions are defined to
>
> strict.

Thanks for the answer. So there are only two options.

1. Create a patch for the package - that means bump up the version in the Cargo.toml and fix all the stuff in the code so that it works. Then send this PR to the project and include the patch in patches directory.

2. Include the required package definition in the Guix cargo-*.scm file even if there is a version similar to the one that I package or if the version is an older one.

The substitution is possible only in rare cases.

This is also probably applicable to other languages, right?
>
> ---------------------------------------------------------------------------------
>
> Regards
>
> Hartmut Goebel
>
> | Hartmut Goebel | h.goebel@crazy-compilers.com |
>
> | www.crazy-compilers.com | compilers which you thought are impossible |


      reply	other threads:[~2021-10-10  7:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-03  7:02 Crates versions and their replacement phodina
2021-10-05 18:19 ` Hartmut Goebel
2021-10-10  7:11   ` phodina [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='ebVG5JKeqV2z0xvaz9mWlVuWOdy6FMZtrNeCJ30MoO7RwQuMOm0lw27gJ7JmHKV7fOE6vPdKM4bZsZtAbjMWTftJMtn8RL5LqXAGF6IvPZQ=@protonmail.com' \
    --to=phodina@protonmail.com \
    --cc=h.goebel@crazy-compilers.com \
    --cc=help-guix@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.
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).