[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: program prepared with `guix pack` unusable by end users

From: zimoun
Subject: Re: program prepared with `guix pack` unusable by end users
Date: Fri, 14 Oct 2022 09:33:49 +0200

Hi, Wojtek,
On jeu., 13 oct. 2022 at 18:20, Wojtek Kosior via <> wrote:

> It took me a couple of minutes to understand what you're talking
> about. Indeed, instead of copy-pasting the <> 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: "(" <>
To: "kiasoc5" <>, <>
References: <>
In-Reply-To: <>
--8<---------------cut here---------------end--------------->8---

and your message in this other thread,

--8<---------------cut here---------------start------------->8---


Received: from [] (
 by with esmtpsa (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.92) (envelope-from <>) id 1oisT6-0007ax-Ue
 for; Thu, 13 Oct 2022 09:17:25 +0200
Date: Thu, 13 Oct 2022 09:17:22 +0200
To: <>
Subject: program prepared with `guix pack` unusable by end users
Message-ID: <>
In-Reply-To: <CNKL38E5T0RV.1VYM8R2V0O1QM@guix-framework>
References: <>
X-Mailer: Claws Mail 3.17.8 (GTK+ 2.24.33; x86_64-pc-linux-gnu)


List-Id: <>
List-Unsubscribe: <>,
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>,
Sender: "Help-Guix" <>
Reply-to:  Wojtek Kosior <>
From:  Wojtek Kosior via <>

--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:


and your message contains the field In-Reply-To


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 "";)
>     (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: <>


reply via email to

[Prev in Thread] Current Thread [Next in Thread]