unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
To: Wojtek Kosior <koszko@koszko.org>
Cc: Gottfried <gottfried@posteo.de>, help-guix@gnu.org
Subject: Re: tor
Date: Tue, 8 Nov 2022 00:19:13 +0100	[thread overview]
Message-ID: <20221108001913.3875f6cc@primary_laptop> (raw)
In-Reply-To: <20221107211430.4145e9bc@koszkonutek-tmp.pl.eu.org>

[-- Attachment #1: Type: text/plain, Size: 2223 bytes --]

On Mon, 7 Nov 2022 21:14:30 +0100
Wojtek Kosior <koszko@koszko.org> wrote:

> > Will this be also at some stage a Guix package or everybody has to 
> > install it as a script?  
> 
> I understand Denis' intention is to ultimately make *the script* into
> a Guix package. But it is possible to have the script look like an
> application and appear in user's applications menu. So in the end
> launching the Tor Browser through it wouldn't be noticeably different
> from running a normal browser.
In my case I've packaged it in my system.scm, so I can run it like
any other program.

I've not added the information (yet) about that as I though that just
making the script work for another setup than mine would require some
work / adjustment.

As for packaging the script in Guix, the main blocker is to find a way
to make sure it is FSDG compliant.

I guess that if it software that is already there, it should be
ok to package the current script, but I'm more interested in having
something that would download, verify, install and run the tor-browser
to make it easy for users to use.

And that for sure requires to make sure that what we download is OK
FSDG wise.

I've found that bug:
https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/14924

So maybe I could drop a line there to explain our issue and why
removing that text would make it ok for any FSDG distributions to
package the tor-browser launcher or similar software (like this script).

>     export
> PATH="$HOME"/.local/share/torbrowser/tbb/x86_64/tor-browser_en-US/Browser/:"$PATH"
> 
> If you instead choose to place the script inside `~/.local/bin`, that
> directory is (probably) going to be included in the `PATH` by default
> (by the means of your default, auto-created shell initialization
> scripts).
I used that path to make it compatible with the tor-browser launcher.

> Although this is not related, I believe the
> `export DISPLAY=${DISPLAY};` trick in the script can be replaced with
> the `--preserve` option of `guix shell`. At this very moment I
> realized I can also improve some code of mine this way :o
Thanks a lot, that could indeed make my code way cleaner.

Denis.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2022-11-07 23:26 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-28 10:52 tor Gottfried
2022-08-28 12:09 ` tor Csepp
2022-08-29 14:19   ` tor Gottfried
2022-08-30 10:54     ` tor Csepp
2022-08-30 18:32       ` tor Gottfried
2022-08-31 16:23         ` tor Denis 'GNUtoo' Carikli
2022-09-01 13:59           ` tor Denis 'GNUtoo' Carikli
2022-09-02 18:31             ` tor Gottfried
2022-09-21  9:52               ` tor Gottfried
2022-09-22 11:52                 ` tor Chris Keschnat via
2022-09-01 14:27         ` tor Denis 'GNUtoo' Carikli
2022-09-01 17:35           ` tor Gottfried
2022-09-01 23:35             ` tor Denis 'GNUtoo' Carikli
2022-11-05  0:29           ` tor Denis 'GNUtoo' Carikli
2022-11-07 19:24             ` tor Gottfried
2022-11-07 20:14               ` tor Wojtek Kosior via
2022-11-07 23:19                 ` Denis 'GNUtoo' Carikli [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-09-23 16:36 tor Gottfried
2020-09-17 12:32 Tor Rasa Gulla via
2020-09-17 13:15 ` Tor Julien Lepiller
2020-09-17 13:18   ` Tor Rasa Gulla

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=20221108001913.3875f6cc@primary_laptop \
    --to=gnutoo@cyberdimension.org \
    --cc=gottfried@posteo.de \
    --cc=help-guix@gnu.org \
    --cc=koszko@koszko.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).