From: Raghav Gururajan <rg@raghavgururajan.name>
To: Leo Prikler <leo.prikler@student.tugraz.at>, 45954@debbugs.gnu.org
Subject: [bug#45954] Telegram-CLI (v7)
Date: Mon, 1 Feb 2021 21:33:43 -0500 [thread overview]
Message-ID: <596596fa-35d4-a7db-d890-153f51728780@raghavgururajan.name> (raw)
In-Reply-To: <515542411e38fa921ef936fe116bd3e0fb2a44d1.camel@student.tugraz.at>
[-- Attachment #1.1.1: Type: text/plain, Size: 2235 bytes --]
Hi Leo!
> I didn't notice this before, but is there a reason to package this
> version over 1.3.1?
Yeah, there are quite a lot of improvements after the 1.3.1 release.
> Please stop trying to use this as a snippet to mean "the root of the
> source and build directory". It is extremely obscure and people are
> already using "../source" just fine. (Just do an rgrep if you aren't
> convinced.)
Fixed in v8.
>> Hmm. I tried but couldn't come up with a way to do it like that. :(
> You can still try harder for v8 ;)
I tried different ways but the arguments key-words between gnu and copy
differ a lot. I am unable use key-words from both build systems at the
same time. Like using #:configure-flags (from gnu) and #:install (from
copy).
Also, I spent significant amount time to come up the phase I have. So if
there are no critical issues, I would like to keep it as-is. :-)
>> 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.
> In that case, does the daemon script have any value of its own? Given
> that the latest release of telegram-cli is about six years old, I doubt
> there is – foreign distros should already have it in their repos and
> Guix as a package manager makes no claim to manage system stuff like
> services on foreign distros.
>
>> The file is a run-time script.
> That means literally nothing. The wrap phase exists for a reason, some
> programs and script are even wrapped twice.
>
>> Using (getenv "PATH") will instead use the value of PATH inside the
>> build environment.
> So you'll inadvertently have some native-inputs in it, is what you're
> trying to say? Of course, there are better ways of wrapping PATH, but
> in this case wouldn't it be wise to limit it to just the expected
> paths? Again, assuming that there is even merit in shipping this file,
> which is yet to be proven.
I don't know what I was thinking. XD. It is pretty useless to ship. I
removed it in v8.
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-02 2:34 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=596596fa-35d4-a7db-d890-153f51728780@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 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.