From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: 宋文武 <iyzsong@envs.net>
Cc: 65550@debbugs.gnu.org, 宋文武 <iyzsong@member.fsf.org>,
"Liliana Marie Prikler" <liliana.prikler@gmail.com>
Subject: [bug#65550] Don't add propagated-inputs for all outputs
Date: Thu, 31 Aug 2023 22:16:25 -0400 [thread overview]
Message-ID: <87msy67i4m.fsf_-_@gmail.com> (raw)
In-Reply-To: <877cpedu3k.fsf@envs.net> ("宋文武"'s message of "Tue, 29 Aug 2023 18:24:31 +0800")
Hi,
宋文武 <iyzsong@envs.net> writes:
> Liliana Marie Prikler <liliana.prikler@gmail.com> writes:
>
>> I'd really like to avoid yet another special output, when "bin", "lib",
>> etc. have already been given clear meanings, one of which strongly
>> overlaps with "stuff that wants propagated inputs for pkg-config
>> reasons".
>
> The benefit to put headers files and libraries files into seperated
> outputs is to reduce the runtime closure size of packages, for example
> my home profile contains xfce, emacs, fonts, etc. has total 5GiB (by
> guix size), and they have 300MiB under include.
>
> calculated by:
>
> x=/gnu/store/0fyhci5kv03rfb9430jqs9wki2ifq5ja-profile
> guix size $x
> for i in `guix size $x`;
> do [ -e $i/include ] && du -sb $i/include;
> done | awk '{ sum += $1 } END { print sum / 1024 / 1024 }'
>
> If put headers and other development files into a "dev" output, then
> those 300MiB can be saved (won't need to be substituted if substitutes
> available). Note that use a "include" output won't help here if you
> leave pkg-config files in "lib", since pkg-config files need reference
> its include and binaries need reference its libraries.
>
> So it seems to me a "dev" output is unavoidable, also both Debian and
> Alpine Linux use '-dev' packages for the same reason, it should be
> familiar to learn..
I'm not convinced that saving 300 MiB on 5 GiB is worth making using
Guix packages more complicated, especially in this age of compressed
file systems (text files compress very well). We'd also have to change
a couple things to make it convenient and not have to plaster the code
base with ugly `(,lib "dev") inputs ^^'.
I reckon it could all be automated, but I'm not sure it's worth the
effort at this stage (there bigger low hanging fruits to pick in my
opinion -- such as moving static libraries automatically in the gnu
build system, paying more attention to large documentation or unecessary
installed files, etc.).
--
Thanks,
Maxim
next prev parent reply other threads:[~2023-09-01 2:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-26 11:36 Don't add propagated-inputs for all outputs 宋文武
2023-08-26 13:53 ` [bug#65550] [PATCH] profiles: Don't propagate inputs for non-development packages iyzsong--- via Guix-patches via
2023-08-26 14:21 ` Liliana Marie Prikler
2023-08-27 7:30 ` 宋文武 via Guix-patches via
2023-08-27 9:31 ` Liliana Marie Prikler
2023-08-29 10:24 ` 宋文武 via Guix-patches via
2023-08-29 17:01 ` Liliana Marie Prikler
2023-08-30 10:55 ` 宋文武 via Guix-patches via
2023-09-01 2:16 ` Maxim Cournoyer [this message]
2023-08-27 7:34 ` Josselin Poiret via Guix-patches via
2023-09-01 2:34 ` [bug#65550] Don't add propagated-inputs for all outputs Maxim Cournoyer
2023-09-01 12:53 ` 宋文武 via Guix-patches via
2023-09-01 15:03 ` Maxim Cournoyer
2023-09-02 0:43 ` bug#65550: " 宋文武 via Guix-patches via
2023-09-09 10:38 ` [bug#65550] [PATCH] profiles: Don't propagate inputs for non-development packages Ludovic Courtès
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=87msy67i4m.fsf_-_@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=65550@debbugs.gnu.org \
--cc=iyzsong@envs.net \
--cc=iyzsong@member.fsf.org \
--cc=liliana.prikler@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.