unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: Zhu Zihao <all_but_last@163.com>
Cc: 55423@debbugs.gnu.org
Subject: [bug#55423] [PATCH]: gnu: Add mogan.
Date: Sun, 15 May 2022 16:24:27 +0200	[thread overview]
Message-ID: <cf0952c23b961650c46008746738b3c0c966216b.camel@telenet.be> (raw)
In-Reply-To: <861qwuzy57.fsf@163.com>

[-- Attachment #1: Type: text/plain, Size: 1445 bytes --]

Zhu Zihao schreef op zo 15-05-2022 om 22:05 [+0800]:
> Yes, it's bundled. But I don't have a plan to unbundle it. It's small
> and we'll have more work to do if we try to unbundle. 

From (guix)Synopses and Descriptions:

  8. Make sure the package does not use bundled copies of software
     already available as separate packages.

     Sometimes, packages include copies of the source code of their
     dependencies as a convenience for users.  However, as a
     distribution, we want to make sure that such packages end up using
     the copy we already have in the distribution, if there is one.
     This improves resource usage (the dependency is built and stored
     only once), and allows the distribution to make transverse changes
     such as applying security updates for a given software package in
     a single place and have them affect the whole system—something
     that bundled copies prevent.

I don't think resource usage is a problem here, but the security
updates and transverse changes bits seem relevant here to me
(also: bug fixes, less redundancy when checking source code for malware
or bugs, replacing the s7 used by applications by a custom one to test
out new features or performance or such, ...)

It's a bit of an investment now that gives some flexibility for the
future and avoids some potential problems (e.g. malware bit and
security updates bit).

Greetings,
Maxime.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

  reply	other threads:[~2022-05-15 14:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-15  3:21 [bug#55423] [PATCH]: gnu: Add mogan Zhu Zihao
2022-05-15 11:57 ` Maxime Devos
2022-05-15 13:56   ` Zhu Zihao
2022-05-15 11:58 ` Maxime Devos
2022-05-15 14:05   ` Zhu Zihao
2022-05-15 14:24     ` Maxime Devos [this message]
2022-05-15 11:59 ` Maxime Devos
2022-05-15 14:12   ` [bug#55423] What's the motivation of creating Mogan. (was Re: [bug#55423] [PATCH]: gnu: Add mogan.) Zhu Zihao
2022-05-16 10:39     ` Darcy Shen via Guix-patches via
2022-09-05 11:41   ` [bug#55423] [PATCH]: gnu: Add mogan Zhu Zihao
2022-09-22  5:40     ` Zhu Zihao
2022-11-07 11:06       ` bug#55423: " Zhu Zihao
2022-05-15 12:01 ` [bug#55423] " 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=cf0952c23b961650c46008746738b3c0c966216b.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=55423@debbugs.gnu.org \
    --cc=all_but_last@163.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).