From: Maxime Devos <maximedevos@telenet.be>
To: Taiju HIGASHI <higashi@taiju.info>
Cc: 55612@debbugs.gnu.org
Subject: [bug#55612] [PATCH 0/2] Update guile-hall to 0.4.1.
Date: Tue, 24 May 2022 16:26:30 +0200 [thread overview]
Message-ID: <d5019147620c82206fa25cf74715bbec30873ecc.camel@telenet.be> (raw)
In-Reply-To: <875ylvqaf9.fsf@taiju.info>
[-- Attachment #1: Type: text/plain, Size: 832 bytes --]
Taiju HIGASHI schreef op di 24-05-2022 om 23:20 [+0900]:
> I see. So separating the packages doesn't solve anything because of the
> conflicts that occur?
Depends on how things are used. If you install two applications (*)
'foo' and 'bar' in the same profile that use different versions of
guile-config: no problem. If you are developing both 'foo' and 'bar'
in the same session, e.g. with "guix shell -D foo -D bar", then there's
a problem because the profile can contain only a single version of
their dependency guile-config (**). Some other problematic variations
are possible too.
(*) Normally applications don't propagate anything, they just put
things in 'inputs' and use sufficient amount of wrapping to avoid
propagation.
(**) IIUC, "guix shell -D" currently silently picks one version or the
other
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-05-24 14:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-24 13:26 [bug#55612] [PATCH 0/2] Update guile-hall to 0.4.1 Taiju HIGASHI
2022-05-24 13:29 ` [bug#55612] [PATCH 1/2] gnu: Add guile-config-0.5 Taiju HIGASHI
2022-05-24 13:29 ` [bug#55612] [PATCH 2/2] gnu: guile-hall: Update to 0.4.1 Taiju HIGASHI
2022-05-24 14:10 ` [bug#55612] [PATCH 0/2] Update guile-hall " Maxime Devos
2022-05-24 14:20 ` Taiju HIGASHI
2022-05-24 14:26 ` Maxime Devos [this message]
2022-05-26 1:10 ` Taiju HIGASHI
2022-06-03 21:23 ` Ludovic Courtès
2022-06-03 22:24 ` Taiju HIGASHI
2022-07-06 8:40 ` Ricardo Wurmus
2022-07-06 13:56 ` Taiju HIGASHI
2022-07-16 11:27 ` Taiju HIGASHI
2022-07-21 15:54 ` bug#55612: " Ricardo Wurmus
2022-07-22 0:05 ` [bug#55612] " Taiju HIGASHI
2022-07-06 13:46 ` [bug#55612] [PATCH v2 1/2] gnu: guile-config: Update to 0.5.1 Taiju HIGASHI
2022-07-06 13:46 ` [bug#55612] [PATCH v2 2/2] gnu: guile-hall: Update to 0.4.1 Taiju HIGASHI
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=d5019147620c82206fa25cf74715bbec30873ecc.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=55612@debbugs.gnu.org \
--cc=higashi@taiju.info \
/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.