all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Bruno Haible <bruno@clisp.org>
Cc: 41037@debbugs.gnu.org
Subject: bug#41037: documentation for application developers?
Date: Sun, 03 May 2020 22:59:43 +0200	[thread overview]
Message-ID: <87pnbkvio0.fsf@gnu.org> (raw)
In-Reply-To: <1614037.PG1mooiXeX@omega> (Bruno Haible's message of "Sun, 03 May 2020 01:36:55 +0200")

HI Bruno,

Bruno Haible <bruno@clisp.org> skribis:

> I'm searching for documentation for application developers, regarding
> tips for porting from ordinary Linux distros to GNU guix.

There’s no such documentation.  However, for applications that follow
“good practices”, there really isn’t any porting to do.

> 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.  What Guix packages do is patch them.

>   - where is /lib/x86_64-linux-gnu/ld-linux-x86-64.so.2 ?

It’s in the glibc package:

  ls $(guix build glibc | grep '[0-9]$')/lib

What’s your use case?

>   - libtool, ldconfig issues

‘ldconfig’ is not used.  Nothing special for Libtool.
Do you have something in mind?

Thanks,
Ludo’.




  reply	other threads:[~2020-05-03 21:00 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 [this message]
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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87pnbkvio0.fsf@gnu.org \
    --to=ludo@gnu.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 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.