From: Gottfried <gottfried@posteo.de>
To: help-guix@gnu.org, Martin Castillo <castilma@uni-bremen.de>
Subject: do old packages like Musescore 3.6.2 need updating?
Date: Fri, 28 Apr 2023 15:15:33 +0000 [thread overview]
Message-ID: <2fc9fd24-163e-db3a-6665-594255194d99@posteo.de> (raw)
[-- Attachment #1.1.1: Type: text/plain, Size: 918 bytes --]
Hi,
1.
I have the old version of Musescore 3.6.2 which I want in one profile.
When I update all profiles at once through a script, it also builds
locally the old version of Musescore, which needs 1 hour on my laptop.
Firstly, why it always builds it on my laptop?
2.
Do old versions of a package also need to be upgraded?
3.
and why it want to build it always on my laptop locally?
I thought old versions of a package don’t need upgrading, because only
new packages develop.
May be I am mistaken.
Do old versions of a package also need upgrading because of some
dependencies?
4.
when I upgrade all profiles at once, but do not want to upgrade
Musescore 3.6.2
what are the possibilities?
Should I put Musescore 3.6.2 as only package in one profile and
exclude this profile from updating?
or is it better sometimes also to upgrade this old package?
Kind regards
Gottfried
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3191 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next reply other threads:[~2023-04-28 16:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-28 15:15 Gottfried [this message]
2023-04-29 13:42 ` do old packages like Musescore 3.6.2 need updating? Martin Castillo
2023-04-29 15:53 ` Gottfried
2023-04-29 15:57 ` Gottfried
2023-05-01 0:25 ` Maxim Cournoyer
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=2fc9fd24-163e-db3a-6665-594255194d99@posteo.de \
--to=gottfried@posteo.de \
--cc=castilma@uni-bremen.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.