all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>
Cc: rg@raghavgururajan.name, Vivien Kraus <vivien@planete-kraus.eu>,
	67473@debbugs.gnu.org
Subject: [bug#67473] [PATCH gnome-team v2 09/13] gnu: Remove libsoup-minimal.
Date: Sun, 03 Dec 2023 20:24:27 -0500	[thread overview]
Message-ID: <87a5qqu5dg.fsf@gmail.com> (raw)
In-Reply-To: <228774cc417536adf9bd649b1d1c7e6009552cbf.camel@gmail.com> (Liliana Marie Prikler's message of "Wed, 29 Nov 2023 17:22:49 +0100")

Hi,

Liliana Marie Prikler <liliana.prikler@gmail.com> writes:

> Am Mittwoch, dem 29.11.2023 um 07:25 +0100 schrieb Vivien Kraus:
>> Le mercredi 29 novembre 2023 à 06:21 +0100, Liliana Marie Prikler a
>> écrit :
>> > Still, there were
>> > other users of libsoup-minimal over libsoup, so we might want to
>> > keep
>> > the variable even as we update both to a new, shared version.
>> I’m tempted to say the users of libsoup-minimal used to depend on
>> libsoup@2, so they put libsoup-minimal-2, but then the package
>> required
>> libsoup@3, and they just removed the "-2" suffix. Is there another
>> reason packages would want a doc-less version of libsoup?
> Closure size?
>
>> I can make another series revision where libsoup-minimal is a
>> deprecated-package pointing to libsoup, or a doc-less libsoup@3. I
>> think the deprecated-package solution is the most useful. What do you
>> think?
> I'd really like a second opinion here.  All I can say is that I don't
> really trust my own gut feeling here.

It appears libsoup and libsoup-minimal closures differs in size by only
little (100 KiB).  So unless there is a requirement here to avoid cycles
(which if there are, would be easy to spot: byte compiling guix would
not complete and bust memory), it could be removed.

-- 
Thanks,
Maxim




      reply	other threads:[~2023-12-04  1:25 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <b946571271d7a4fd62bcc5ddb1b6f1a7b7a8af9a.1701174883.git.vivien@planete-kraus.eu>
2023-11-14 11:35 ` [bug#67473] [PATCH gnome-team v2 02/13] gnu: glib-networking: Update to 2.76.1 Vivien Kraus via Guix-patches via
2023-11-14 20:17 ` [bug#67473] [PATCH gnome-team v2 03/13] gnu: gnome-backgrounds: Update to 44.0 Vivien Kraus via Guix-patches via
2023-11-23 18:22 ` [bug#67473] [PATCH gnome-team v2 04/13] gnu: gtk+: Update to 3.24.38 Vivien Kraus via Guix-patches via
2023-11-23 18:32 ` [bug#67473] [PATCH gnome-team v2 05/13] gnu: gtkmm-3: Update to 3.24.8 Vivien Kraus via Guix-patches via
2023-11-23 23:08 ` [bug#67473] [PATCH gnome-team v2 06/13] gnu: json-glib: Update to 1.6.6 Vivien Kraus via Guix-patches via
2023-11-23 23:37 ` [bug#67473] [PATCH gnome-team v2 07/13] gnu: libnotify: Update to 0.8.3 Vivien Kraus via Guix-patches via
2023-11-23 23:58 ` [bug#67473] [PATCH gnome-team v2 08/13] gnu: libsoup: Update to 3.4.4 Vivien Kraus via Guix-patches via
2023-11-24 22:31 ` [bug#67473] [PATCH gnome-team v2 10/13] gnu: mm-common: Update to 1.0.5 Vivien Kraus via Guix-patches via
2023-11-26 15:18 ` [bug#67473] [PATCH gnome-team v2 11/13] gnu: pangomm@2.46: Update to 2.46.3 Vivien Kraus via Guix-patches via
2023-11-26 18:01 ` [bug#67473] [PATCH gnome-team v2 12/13] gnu: yelp-tools: Update to 42.1 Vivien Kraus via Guix-patches via
2023-11-26 18:02 ` [bug#67473] [PATCH gnome-team v2 13/13] gnu: yelp-xsl: " Vivien Kraus via Guix-patches via
2023-11-28  7:24 ` [bug#67473] [PATCH gnome-team v2 09/13] gnu: Remove libsoup-minimal Vivien Kraus via Guix-patches via
2023-11-28 20:05   ` Liliana Marie Prikler
2023-11-28 21:26     ` Vivien Kraus via Guix-patches via
2023-11-29  5:21       ` Liliana Marie Prikler
2023-11-29  6:25         ` Vivien Kraus via Guix-patches via
2023-11-29 16:22           ` Liliana Marie Prikler
2023-12-04  1:24             ` Maxim Cournoyer [this message]

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=87a5qqu5dg.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=67473@debbugs.gnu.org \
    --cc=liliana.prikler@gmail.com \
    --cc=rg@raghavgururajan.name \
    --cc=vivien@planete-kraus.eu \
    /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.