From: Danny Milosavljevic <dannym@scratchpost.org>
To: Bruno Haible <bruno@clisp.org>
Cc: 41037@debbugs.gnu.org
Subject: bug#41037: documentation for application developers?
Date: Sun, 3 May 2020 23:48:33 +0200 [thread overview]
Message-ID: <20200503234833.3f078d0e@scratchpost.org> (raw)
In-Reply-To: <10121112.yT0VcRYgiK@omega>
[-- Attachment #1: Type: text/plain, Size: 1066 bytes --]
Hi Bruno,
On Sun, 03 May 2020 23:13:46 +0200
Bruno Haible <bruno@clisp.org> wrote:
> So, the consequence is that a Guix user cannot send an executable
> to another Guix user and expect it to be runnable on the other machine.
Do you mean only one file, the executable? That doesn't work well with any
other distribution either.
What guix can do is pack everything a package needs into a tarball
(including dependencies too) and then put that on another machine.
The command is "guix pack" (it can also create Docker containers
and Singularity images--but regular tarballs work just fine).
That does work reliably, and automatically does deduplication.
> I wanted to have background information regarding ldconfig and shared
> library caches, in order to investigate bug#41038
> <https://lists.gnu.org/archive/html/bug-guix/2020-05/msg00036.html>.
ldconfig is not used in Guix. Guix uses rpath in order to embed the
entire path to each of the shared libraries that are used into the
executable.
ldconfig's name resolution is disabled.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-05-03 21:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-02 23:36 bug#41037: documentation for application developers? Bruno Haible
2020-05-03 20:59 ` Ludovic Courtès
2020-05-03 21:13 ` Bruno Haible
2020-05-03 21:48 ` Danny Milosavljevic [this message]
2020-05-03 22:57 ` Bruno Haible
2020-05-03 22:18 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-05-04 8:18 ` 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
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=20200503234833.3f078d0e@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=41037@debbugs.gnu.org \
--cc=bruno@clisp.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).