all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Csepp <raingloom@riseup.net>
To: Gottfried <gottfried@posteo.de>
Cc: Csepp <raingloom@riseup.net>, help-guix@gnu.org
Subject: Re: installing of two versions of package Musescore
Date: Thu, 22 Dec 2022 15:47:24 +0100	[thread overview]
Message-ID: <878riz5vzv.fsf@riseup.net> (raw)
In-Reply-To: <456e159d-4aad-b094-7db7-1b1d45dc23e9@posteo.de>


Gottfried <gottfried@posteo.de> writes:

> [[PGP Signed Part:Undecided]]
> Hi Csepp
>
> thanks for your answer
>
>> I'd leave 3.6.2 in my default profile.
>
> Does this mean, every time I am doing a
>
> guix pull
>
> and
>
> guix package --upgrade
>
> I have to add:
>
>  --do-not-upgrade musescore
>
> so that musescore stays at the version 3.6.2 ?
>
> (If I forget to add this, than it will upgrade to version 3.4
> and I can than only switch back one generation and do the
> guix package --upgrade --do-not-upgrade musescore
> again)
> Is it like this?
>
> Gottfried

Well, it will also not upgrade its dependencies in that case.  If you
want to use an old version forever, sure, you can use --do-not-upgrade,
but you could also pin the source to an old version.
For that you would use the --with-branch=musescore=v3.6.2
transformation... I think.
I recommend reading the info page on defining package variants.


  reply	other threads:[~2022-12-22 14:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-19  8:23 installing of two versions of package Musescore Gottfried
2022-12-19 13:55 ` Csepp
2022-12-19 14:19   ` Gottfried
2022-12-20 17:02     ` Csepp
2022-12-21 13:17       ` Gottfried
2022-12-21 18:06         ` Csepp
2022-12-22 13:21           ` Gottfried
2022-12-22 14:47             ` Csepp [this message]
2022-12-21 18:53         ` Wojtek Kosior via
2022-12-24 14:08       ` Gottfried
2022-12-26 18:33         ` Wojtek Kosior via
2022-12-27 11:30           ` Csepp

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=878riz5vzv.fsf@riseup.net \
    --to=raingloom@riseup.net \
    --cc=gottfried@posteo.de \
    --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.
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.