From: Tobias Geerinckx-Rice via Guix-patches via <guix-patches@gnu.org>
To: zimoun <zimon.toutoune@gmail.com>
Cc: paren@disroot.org, 58583@debbugs.gnu.org, maxim.cournoyer@gmail.com
Subject: [bug#58583] [PATCH 0/1] scripts: package: Forbid installation of the guix package.
Date: Fri, 28 Oct 2022 18:20:06 +0200 [thread overview]
Message-ID: <87r0yrzzht.fsf@nckx> (raw)
In-Reply-To: <86a65g8k9a.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 984 bytes --]
Heyo,
zimoun 写道:
> Not necessary or I am missing something. For instance, you want
> to
> build some Guile application relying on the Guix library;
> similarly as
> you have, say, guile-commonmark or any other Guile packages.
Sure.
> Yes, it is possible to do without installing the package guix
> but it is
> not handy. Aside, it is not always clear which revision of the
> API is
> available when the package guix fixes it.
OK. But could you explain more clearly how
$ guix install guix
is involved, and how it is ‘handy’?
How does one continue to use guix *as a package manager*, having
now silently broken ‘guix pull’?
> For instance, if an user packs their Guile application using
> some other
> Guile libraries including the Guix library, then for developing,
> it
> becomes not possible to just locally create a profile.
Why not?
> But maybe I am missing something.
Or we are!
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2022-10-28 16:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-17 12:16 [bug#58583] [PATCH 0/1] scripts: package: Forbid installation of the guix package ( via Guix-patches via
2022-10-17 12:18 ` [bug#58583] [PATCH 1/1] " ( via Guix-patches via
2022-10-17 12:22 ` [bug#58583] [PATCH v2] " ( via Guix-patches via
2022-10-17 16:24 ` Tobias Geerinckx-Rice via Guix-patches via
2022-10-17 16:43 ` ( via Guix-patches via
2022-10-17 16:50 ` [bug#58583] [PATCH v3] " ( via Guix-patches via
2022-10-17 18:14 ` zimoun
2022-10-27 20:04 ` [bug#58583] [PATCH 0/1] " Maxim Cournoyer
2022-10-28 7:44 ` zimoun
2022-10-28 14:31 ` ( via Guix-patches via
2022-10-28 15:47 ` Maxim Cournoyer
2022-10-28 16:20 ` Tobias Geerinckx-Rice via Guix-patches via [this message]
2022-10-28 17:01 ` Tobias Geerinckx-Rice via Guix-patches via
2022-11-02 11:47 ` zimoun
2022-11-02 13:19 ` Tobias Geerinckx-Rice via Guix-patches via
2022-11-02 15:48 ` zimoun
2022-11-03 15:03 ` Maxim Cournoyer
2022-11-03 18:32 ` zimoun
2022-10-27 20:11 ` 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=87r0yrzzht.fsf@nckx \
--to=guix-patches@gnu.org \
--cc=58583@debbugs.gnu.org \
--cc=maxim.cournoyer@gmail.com \
--cc=me@tobias.gr \
--cc=paren@disroot.org \
--cc=zimon.toutoune@gmail.com \
/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.