From: Pierre Neidhardt <mail@ambrevar.xyz>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: "Ludovic Courtès" <ludo@gnu.org>, 42576@debbugs.gnu.org
Subject: [bug#42576] [PATCH 1/2] gnu: llvm: Move dynamic libraries to a separate "lib" output.
Date: Sat, 01 Aug 2020 13:18:03 +0200 [thread overview]
Message-ID: <878seyaa38.fsf@ambrevar.xyz> (raw)
In-Reply-To: <20200801125953.2e898f63@scratchpost.org>
[-- Attachment #1: Type: text/plain, Size: 675 bytes --]
Hi Danny!
Danny Milosavljevic <dannym@scratchpost.org> writes:
> Hmm, glib for example moves the binaries to a "bin" output while retaining the
> libraries in "out".
>
> Any reason this patch moves the libraries and not the binaries?
Ludo suggested this way I think out of consistency with the rest.
> Also, I would have thought that those llvm programs reference the llvm
> libraries anyway, and thus in the end no space could be saved. Is this
> not the case?
This patch not about saving space for LLVM programs, but packages that depend
on LLVM libraries and which don't need the programs.
Cheers!
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2020-08-01 11:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-28 9:58 [bug#42576] [PATCH 1/2] gnu: llvm: Move dynamic libraries to a separate "lib" output Pierre Neidhardt
2020-07-28 10:03 ` [bug#42576] [PATCH 2/2] gnu: llvm-3.9.1: Move libraries to " Pierre Neidhardt
[not found] ` <handler.42576.B.159593032321168.ack@debbugs.gnu.org>
2020-07-28 10:07 ` [bug#42576] Acknowledgement ([PATCH 1/2] gnu: llvm: Move dynamic libraries to a separate "lib" output.) Pierre Neidhardt
2020-08-01 10:59 ` [bug#42576] [PATCH 1/2] gnu: llvm: Move dynamic libraries to a separate "lib" output Danny Milosavljevic
2020-08-01 11:18 ` Pierre Neidhardt [this message]
2020-08-07 18:09 ` Jakub Kądziołka
2020-08-08 8:49 ` Pierre Neidhardt
2021-09-24 0:41 ` Sarah Morgensen
2021-09-24 7:10 ` Pierre Neidhardt
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=878seyaa38.fsf@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--cc=42576@debbugs.gnu.org \
--cc=dannym@scratchpost.org \
--cc=ludo@gnu.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.
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).