From: Maxime Devos <maximedevos@telenet.be>
To: Philip McGrath <philip@philipmcgrath.com>,
Liliana Marie Prikler <liliana.prikler@gmail.com>,
57683@debbugs.gnu.org
Subject: [bug#57683] [PATCH] gnu: zuo: Use mirrored repository.
Date: Mon, 19 Sep 2022 15:53:43 +0200 [thread overview]
Message-ID: <42f7a392-4716-eba7-d237-0241b3f8fada@telenet.be> (raw)
In-Reply-To: <a9beb36a-797d-f6c2-587c-09fd0c862a51@philipmcgrath.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 1386 bytes --]
> https://docs.racket-lang.org/zuo/
The documentation sounds better as a home page to me than a link to the
source code.
On 19-09-2022 04:06, Philip McGrath wrote:
> When I hear the word "unbundle", I think of configuring Racket and Chez
> Scheme to use our shared Zlib and removing their vendored copies. I
> don't see how the concept applies usefully to the scenario of multiple
> pieces of software, some of which are useful independently, being
> developed upstream in the same source tree. Like, what would it mean to
> "unbundle" gfortran from gcc?
In case of gcc, I think updating the components separately doesn't make
much sense (from what I hear, it's the same situation for Racket and
Zuo, where 'Zuo' is just a component of Racket, not something
independent that's 'merely' a dependency of Racket).
However, for gcc, _building_ the components in separately does IMHO --
many users don't need GCC's Go or Fortran compiler, so they are separate
packages. However, IIUC, currently when building gccgo and gfortran it
also rebuilds the internal dependencies like libiberty and libgcc and
such, which is inefficient, so I think it would be nice to eventually
split the gcc package in its individual component (but sharing a single
origin!).
(I don't know if the second paragraph applies to Racket and Zuo.)
Greetings,
Maxime.
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 929 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
next prev parent reply other threads:[~2022-09-19 13:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-08 17:27 [bug#57683] [PATCH] gnu: zuo: Use mirrored repository Liliana Marie Prikler
2022-09-09 12:42 ` Maxime Devos
2022-09-09 12:55 ` Liliana Marie Prikler
2022-09-19 2:06 ` Philip McGrath
2022-09-19 13:53 ` Maxime Devos [this message]
2022-09-19 18:33 ` Liliana Marie Prikler
2022-09-19 18:40 ` Maxime Devos
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=42f7a392-4716-eba7-d237-0241b3f8fada@telenet.be \
--to=maximedevos@telenet.be \
--cc=57683@debbugs.gnu.org \
--cc=liliana.prikler@gmail.com \
--cc=philip@philipmcgrath.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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).