Github messages for voidlinux
 help / color / mirror / Atom feed
From: nekopsykose <nekopsykose@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: mesa-demos: update to 9.0.0.
Date: Sat, 25 Mar 2023 01:30:30 +0100	[thread overview]
Message-ID: <20230325003030.VJnBpA9a44W89Wylt-YsdDGmpqEbiDCd_5wFMlVnsSA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42959@inbox.vuxu.org>

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

New comment by nekopsykose on void-packages repository

https://github.com/void-linux/void-packages/pull/42959#issuecomment-1483633840

Comment:
> The package size really ballooned up with this upgrade, not sure if it's cause for concern.The package size really ballooned up with this upgrade, not sure if it's cause for concern.  

i noticed this as well a long time ago- it balloons between 8.4 and 8.5 too. not sure if it's the meson setup that causes it, or something else. i'd imagine one can do some elf inspection by hand to see what uses it before/after on a specific binary.

the individual binaries (that do the same thing) go from like e.g. 20k to 200k each, etc

  parent reply	other threads:[~2023-03-25  0:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-23 22:19 [PR PATCH] " mhmdanas
2023-03-23 22:21 ` [PR REVIEW] " mhmdanas
2023-03-25  0:30 ` nekopsykose [this message]
2023-03-27  6:41 ` classabbyamp
2023-04-04 20:35 ` mhmdanas
2023-04-04 20:42 ` classabbyamp
2023-06-26 11:04 ` [PR PATCH] [Updated] " mhmdanas
2023-09-25  1:45 ` github-actions
2023-10-10  1:45 ` [PR PATCH] [Closed]: " github-actions

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=20230325003030.VJnBpA9a44W89Wylt-YsdDGmpqEbiDCd_5wFMlVnsSA@z \
    --to=nekopsykose@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /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.
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 NNTP newsgroup(s).