From: ng0 <ng0@n0.is>
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: $out/lib/libexec?
Date: Mon, 25 Nov 2019 19:48:00 +0000 [thread overview]
Message-ID: <20191125194800.ge5l3rdxbw2oualv@uptimegirl> (raw)
In-Reply-To: <9e4cbb94-07f4-0fcd-a093-6071e3c94709@crazy-compilers.com>
I would leave it as it is, some applications require this layout,
I can only speak for what I work on - as it behaves this way - gnunet,
which would require too much to adjust to some arbitrary layout choice.
next prev parent reply other threads:[~2019-11-25 19:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-25 19:21 $out/lib/libexec? Hartmut Goebel
2019-11-25 19:48 ` ng0 [this message]
2019-11-26 10:32 ` $out/lib/libexec? Ludovic Courtès
2019-11-26 10:47 ` $out/lib/libexec? Hartmut Goebel
2019-11-26 13:54 ` $out/lib/libexec? ng0
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=20191125194800.ge5l3rdxbw2oualv@uptimegirl \
--to=ng0@n0.is \
--cc=guix-devel@gnu.org \
--cc=h.goebel@crazy-compilers.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.