From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: $out/lib/libexec?
Date: Tue, 26 Nov 2019 11:47:01 +0100 [thread overview]
Message-ID: <1996d1fe-c3e1-557a-4582-aa167e5af146@crazy-compilers.com> (raw)
In-Reply-To: <87imn77wt3.fsf@gnu.org>
Hi,
Am 26.11.19 um 11:32 schrieb Ludovic Courtès:
> IMO it would be nicer to have them install things to $out/libexec.
Given ng0's comment, I'll not put time into this for now.
--
Regards
Hartmut Goebel
| Hartmut Goebel | h.goebel@crazy-compilers.com |
| www.crazy-compilers.com | compilers which you thought are impossible |
next prev parent reply other threads:[~2019-11-26 10:47 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 ` $out/lib/libexec? ng0
2019-11-26 10:32 ` $out/lib/libexec? Ludovic Courtès
2019-11-26 10:47 ` Hartmut Goebel [this message]
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
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=1996d1fe-c3e1-557a-4582-aa167e5af146@crazy-compilers.com \
--to=h.goebel@crazy-compilers.com \
--cc=guix-devel@gnu.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).