From: Raghav Gururajan <rg@raghavgururajan.name>
To: Leo Prikler <leo.prikler@student.tugraz.at>, 45954@debbugs.gnu.org
Subject: [bug#45954] Telegram-CLI (v6)
Date: Mon, 1 Feb 2021 17:18:05 -0500 [thread overview]
Message-ID: <494758df-748b-7f1d-5f69-45d80cdaa0e8@raghavgururajan.name> (raw)
In-Reply-To: <f2529b6a7dfd934349b57bf1d52802fa7f41a532.camel@student.tugraz.at>
[-- Attachment #1.1.1: Type: text/plain, Size: 1138 bytes --]
Hi Leo!
> The commit does not match up with the version. If this is intended,
> use git-version instead.
Changed in v7.
> You might want to write that in terms of copy-build-system.
Hmm. I tried but couldn't come up with a way to do it like that. :(
> Same here. Also, I'm not sure if SysV init scripts are that compatible
> with Guix running on Shepherd. Is there a more direct way of launching
> the daemon?
Updated git-version in v7.
The script may only be used on foreign-distro for now. For guix system,
we need to define a service for it.
Also, running telegram-cli doesn't require daemon, but vice-versa. The
daemon is intended to be a complimentary feature to run telegram-cli on
headless server.
> Not that it makes much of a difference, as I doubt this file will still
> be needed, but PATH=$PATH is a noop. Perhaps you want (getenv "PATH")
> instead?
I don't think so. The file is a run-time script. So the script will use
the value of env-var PATH provided by the system. Using (getenv "PATH")
will instead use the value of PATH inside the build environment.
Regards,
RG.
[-- Attachment #1.1.2: OpenPGP_0x5F5816647F8BE551.asc --]
[-- Type: application/pgp-keys, Size: 2649 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
next prev parent reply other threads:[~2021-02-01 22:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-18 9:16 [bug#45954] Telegram-CLI Raghav Gururajan
2021-01-19 15:08 ` [bug#45954] Telegram-CLI (v2) Raghav Gururajan
2021-01-20 10:44 ` [bug#45954] Telegram-CLI (v3) Raghav Gururajan
2021-01-22 4:44 ` [bug#45954] Telegram-CLI (v4) Raghav Gururajan
2021-01-28 1:00 ` [bug#45954] Telegram-CLI (v5) Raghav Gururajan
2021-01-31 19:46 ` [bug#45954] Telegram-CLI (v6) Raghav Gururajan
2021-02-01 8:30 ` Leo Prikler
2021-02-01 22:18 ` Raghav Gururajan [this message]
2021-02-01 22:08 ` [bug#45954] Telegram-CLI (v7) Raghav Gururajan
2021-02-01 22:39 ` Leo Prikler
2021-02-02 2:33 ` Raghav Gururajan
2021-02-02 9:50 ` [bug#45954] Telegram-CLI (v7/v8) Leo Prikler
2021-02-03 2:41 ` Raghav Gururajan
2021-02-02 2:25 ` [bug#45954] Telegram-CLI (v8) Raghav Gururajan
2021-02-03 1:56 ` [bug#45954] Telegram-CLI (v9) Raghav Gururajan
2021-02-03 8:16 ` Leo Prikler
2021-02-03 17:52 ` Raghav Gururajan
2021-02-03 17:50 ` [bug#45954] Telegram-CLI (v10) Raghav Gururajan
2021-02-03 18:18 ` bug#45954: " Leo Prikler
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=494758df-748b-7f1d-5f69-45d80cdaa0e8@raghavgururajan.name \
--to=rg@raghavgururajan.name \
--cc=45954@debbugs.gnu.org \
--cc=leo.prikler@student.tugraz.at \
/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).