From: Alex Kost <alezost@gmail.com>
To: Arun Isaac <arunisaac@systemreboot.net>
Cc: "help-guix@gnu.org" <help-guix@gnu.org>
Subject: Re: transmission-remote-cli not symlinked in ~/.guix-profile/bin/
Date: Mon, 22 Aug 2016 21:51:48 +0300 [thread overview]
Message-ID: <87r39ghc1n.fsf@gmail.com> (raw)
In-Reply-To: <8737lx89hk.fsf@systemreboot.net> (Arun Isaac's message of "Mon, 22 Aug 2016 14:29:35 +0530")
Arun Isaac (2016-08-22 11:59 +0300) wrote:
> I installed the package `transmission-remote-cli` in my profile with
> `guix package -i transmission-remote-cli`. But, the executable
> `transmission-remote-cli` is not symlinked into
> ~/.guix-profile/bin/.
Are you sure you did "guix package -i transmission-remote-cli" as user?
I've just tried and got "~/.guix-profile/bin/transmission-remote-cli"
(it is a symlink to a wrapper but it doesn't matter), so most likely you
did something wrong.
> I have noticed similar problems in some other packages as well. How does
> guix decide which executables to symlink into bin?
If you run "guix build transmission-remote-cli", you'll see:
/gnu/store/...-transmission-remote-cli-1.7.1
Now if you look at this directory, you'll see "bin" directory there.
All files placed in such "bin" directories appears in
"~/.guix-profile/bin" when you install packages. The same for other
directories and files: symlinks to all of them are created for inside
profile after a package is installed.
--
Alex
prev parent reply other threads:[~2016-08-22 18:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-22 8:59 transmission-remote-cli not symlinked in ~/.guix-profile/bin/ Arun Isaac
2016-08-22 18:28 ` Leo Famulari
2016-08-23 5:35 ` Arun Isaac
2016-08-23 10:06 ` Alex Kost
2016-08-23 11:22 ` Arun Isaac
2016-08-23 15:38 ` Leo Famulari
2016-08-24 7:58 ` Arun Isaac
2016-08-24 8:02 ` Arun Isaac
2016-08-24 8:28 ` Alex Kost
2016-08-24 17:11 ` Arun
2016-08-24 17:27 ` Leo Famulari
2016-08-24 19:29 ` Arun
2016-08-24 19:54 ` Leo Famulari
2016-08-24 20:28 ` Leo Famulari
2016-08-22 18:51 ` Alex Kost [this message]
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=87r39ghc1n.fsf@gmail.com \
--to=alezost@gmail.com \
--cc=arunisaac@systemreboot.net \
--cc=help-guix@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.
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).