Hi, Wojtek,
On jeu., 13 oct. 2022 at 18:20, Wojtek Kosior via <help-guix@gnu.org> wrote:
> It took me a couple of minutes to understand what you're talking
> about. Indeed, instead of copy-pasting the <help-guix@gnu.org> address
> I clicked "Reply" on some random email from Guix mailing list and
> changed the subject. For years I've been certain that messages are
> categorized into threads by their subject. Now, as you wrote this, I
> assume there must be some thread meta-data that is invisibly sent by
> our user agents when we use "Reply" or "Reply all".
>
> Who would have thought? In the past, when I saw email software nicely
> present thread emails as a tree of responses, I was thinking "wow,
> this program must be using some really successful heuristic for
> determining what is the response to what". Lol
The header of an email contains many information, for example the one
you replied in the other thread,
--8<---------------cut here---------------start------------->8---
[...]
Date: Thu, 13 Oct 2022 07:33:06 +0100
Message-Id: <CNKL38E5T0RV.1VYM8R2V0O1QM@guix-framework>
Subject: Re: Greetd autologin?
From: "(" <pa...@disroot.org>
To: "kiasoc5" <kias...@disroot.org>, <help-guix@gnu.org>
References: <ab7e4e012324af3f1fc7968742168...@disroot.org>
In-Reply-To: <ab7e4e012324af3f1fc7968742168...@disroot.org>
[...]
--8<---------------cut here---------------end--------------->8---
and your message in this other thread,
--8<---------------cut here---------------start------------->8---
[...]
Received: from [77.252.47.255] (helo=koszkonutek-tmp.pl.eu.org)
by koszko.org with esmtpsa (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
(Exim 4.92) (envelope-from <kos...@koszko.org>) id 1oisT6-0007ax-Ue
for help-guix@gnu.org; Thu, 13 Oct 2022 09:17:25 +0200
Date: Thu, 13 Oct 2022 09:17:22 +0200
To: <help-guix@gnu.org>
Subject: program prepared with `guix pack` unusable by end users
Message-ID: <20221013091722.59d9e...@koszkonutek-tmp.pl.eu.org>
In-Reply-To: <CNKL38E5T0RV.1VYM8R2V0O1QM@guix-framework>
References: <ab7e4e012324af3f1fc7968742168...@disroot.org>
<CNKL38E5T0RV.1VYM8R2V0O1QM@guix-framework>
X-Mailer: Claws Mail 3.17.8 (GTK+ 2.24.33; x86_64-pc-linux-gnu)
[...]
List-Id: <help-guix.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/help-guix>,
<mailto:help-guix-requ...@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/help-guix>
List-Post: <mailto:help-guix@gnu.org>
List-Help: <mailto:help-guix-requ...@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/help-guix>,
<mailto:help-guix-requ...@gnu.org?subject=subscribe>
Errors-To: help-guix-bounces+larch=yhetil....@gnu.org
Sender: "Help-Guix" <help-guix-bounces+larch=yhetil....@gnu.org>
Reply-to: Wojtek Kosior <kos...@koszko.org>
From: Wojtek Kosior via <help-guix@gnu.org>
[...]
--8<---------------cut here---------------end--------------->8---
and such headers are hidden by most of mail clients.
Quickly said, the thread is built using the fields Message-ID and
In-Reply-To. If you give a look at the header of the message you
answered, it contains the Message-ID field:
CNKL38E5T0RV.1VYM8R2V0O1QM@guix-framework
and your message contains the field In-Reply-To
CNKL38E5T0RV.1VYM8R2V0O1QM@guix-framework
and that chain builds the thread, somehow.
> Doing as you requested. Although this is suboptimal as well since now
> the topic is split between 2 threads :/
Communication is never optimal. ;-)
>> Why do you pack ’hydrilla-dist-tarball’ instead of just ’hydrilla’.
>>
>> Guix should take care of everything; not necessary when packing a
>> Python bundle as you are doing.
>
> It's ok, `hydrilla-dist-tarball` refers to a package that is built in
> the package in the normal Guix way. The name just indicates that
> tarball generated under `./dist/` is used instead of the project file
> tree. If you're curious, I explain the crazy details in my previous
> email response to "(".
I am confused because, if I understand correctly, this tarball generated
under ./dist is built using ’python3 -m build -s’, so from my
understanding it is not the “normal Guix way”.
> It sometimes happens that to keep my message concise I write what seems
> to be the most important and attach links to other stuff that the
> reader can look at to understand everything. Here that "stuff" was the
> project repo which contains hydrilla.scm with both package definitions.
>
> And most of the time I learn that I failed to be clear enough and that
> people don't have time to read my links. Well, I'm sorry for the
> confusion. Although I'm starting to lose hope that I will learn to
> communicate with ppl online without so many misunderstandings :/
Communication, especially when we are not native English, is not
straightforward. :-)
> The hydrilla.scm that I was loading with `-L .` is now attached. Is
> there anything wrong in it?
Thanks. Note that I have already given a look before answering you. ;-)
> ;; Use this variant when building from a downloaded release tarball.
> (define-public hydrilla
> (package
> (name "hydrilla")
> (version %hydrilla-version)
> (source (local-file %source-dir #:recursive? #t))
> (build-system python-build-system)
> (arguments
> `(#:phases
> (modify-phases %standard-phases
> (replace 'check
> (lambda* (#:key tests? #:allow-other-keys)
> (when tests?
> (invoke "pytest")))))))
> (propagated-inputs
> (list mitmproxy
> python-beautifulsoup4
> python-click
> python-flask-for-haketilo
> python-gnupg
> python-html5lib
> python-immutables-for-haketilo
> python-itsdangerous
> python-jsonschema
> reuse))
> (native-inputs
> (list python-setuptools-scm
> python-babel
> python-pytest
> python-pypa-build
> python-mypy
> python-types-requests))
> (home-page "https://hydrillabugs.koszko.org/projects/haketilo/wiki";)
> (synopsis "Block JavaScript and add custom logic to web pages")
> (description "Haketilo HTTP proxy facilitates viewing of websites while
> having their original JavaScript replaced by user-provided scripts. Haketilo
> combines the functionalities of content blocker and user script manager. It
> can
> be used with its script repository, Hydrilla.")
> (license (list license:agpl3+ license:gpl3+ license:cc0))))
The point is to pack this definition…
> ;; Use this variant when building from a tarball generated under dist/. This
> ;; can be used to build from a git checkout after running `python3 -m build
> -s`
> ;; or similar.
> (define-public hydrilla-dist-tarball
> (let ((base hydrilla)
> (filename (string-append "hydrilla-" %hydrilla-version ".tar.gz")))
> (package
> (inherit base)
> (source (local-file
> (string-append %source-dir "/dist/" filename))))))
…instead of this one.
Could you give a try? Something along the commands proposed by ’(’ in
[1].
1: <https://yhetil.org/guix/CNKNI3CYETFG.2QP3RDK7DF7PD@guix-framework>
Cheers,
simon
