unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
Cc: 41037@debbugs.gnu.org
Subject: bug#41037: documentation for application developers?
Date: Mon, 04 May 2020 00:18:05 +0200	[thread overview]
Message-ID: <87imhcr7jg.fsf@nckx> (raw)
In-Reply-To: <10121112.yT0VcRYgiK@omega>

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

Hi Bruno!

Bruno Haible 写道:
> Hi Ludo,
>
>> > I would expect to find these issues discussed, at least:
>> >   - hard-coded program names like /bin/pwd
>> 
>> These should be avoided; it’s not Guix-specific, but the 
>> problem is
>> obviously more acute here.
>
> /bin/pwd exists on all other Unix systems; so de facto it _is_ 
> Guix
> specific.

Perhaps.  Well behaved portable programmes use $PATH anyway, so 
it's a non-issue.

A handful hard-code directories at their peril and suffer the 
consequences — usually, by being patched to respect $PATH. :-)

This is deliberately not supported.  Users *could* ask Guix to 
create a /bin/pwd for them.  Nobody does.

> 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.

s|Guix|GNU/Linux|g

> This too is Guix specific; maybe it is already documented?

It's not Guix-specific at all.  It's universal to all unix systems 
(and beyond): when you send someone a binary that's missing 
external dependencies, it will not run.  If you give them the 
dependencies (for example, using ‘guix pack’ which includes the 
correct linker, not someone else's random copy with the same 
name), it runs.  Guix is no different.

> ldconfig and shared library caches

Guix uses neither, since there's nothing to cache: once linked 
(using rpath and absolute /gnu/store file names), libraries do not 
move around in space and time.  It's not the cause of or the 
solution to your problem.  I hope Ludo's suggestion was!

Kind regards,

T G-R

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

  parent reply	other threads:[~2020-05-03 22:18 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
2020-05-03 22:57       ` Bruno Haible
2020-05-03 22:18     ` Tobias Geerinckx-Rice via Bug reports for GNU Guix [this message]
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=87imhcr7jg.fsf@nckx \
    --to=bug-guix@gnu.org \
    --cc=41037@debbugs.gnu.org \
    --cc=me@tobias.gr \
    /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).