From: zimoun <zimon.toutoune@gmail.com>
To: Wojtek Kosior <koszko@koszko.org>, help-guix@gnu.org
Subject: Re: program prepared with `guix pack` unusable by end users
Date: Thu, 13 Oct 2022 15:19:50 +0200 [thread overview]
Message-ID: <87lepjrhc9.fsf@gmail.com> (raw)
In-Reply-To: <20221013091722.59d9ecc0@koszkonutek-tmp.pl.eu.org>
Hi,
Is it related to the message [1] you are answering?
1: <https://yhetil.org/guix/CNKL38E5T0RV.1VYM8R2V0O1QM@guix-framework/>
If no, please start a new thread when it is a new topic. :-)
On jeu., 13 oct. 2022 at 09:17, Wojtek Kosior via <help-guix@gnu.org> wrote:
> I made the pack by running
>
>> guix environment -L . -e '(@ (hydrilla) hydrilla)' -- python3 -m build -s
>> guix pack -L . -RR \
>> -S /hydrilla=bin/hydrilla \
>> -S /hydrilla-builder=bin/hydrilla-builder \
>> -S /hydrilla-server=bin/hydrilla-server \
>> -S /haketilo=bin/haketilo \
>> -e '(@ (hydrilla) hydrilla-dist-tarball)'
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.
Cheers,
simon
next prev parent reply other threads:[~2022-10-13 13:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 6:26 Greetd autologin? kiasoc5
2022-10-13 6:33 ` (
2022-10-13 7:17 ` program prepared with `guix pack` unusable by end users Wojtek Kosior via
2022-10-13 8:26 ` (
2022-10-13 9:51 ` Wojtek Kosior via
2022-10-13 13:19 ` zimoun [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-10-13 16:20 Wojtek Kosior via
2022-10-13 17:34 ` (
2022-10-14 7:33 ` zimoun
2022-10-14 9:09 ` Wojtek Kosior via
2022-10-14 11:00 ` zimoun
2022-10-17 13:36 ` Wojtek Kosior via
2022-10-26 7:23 ` Wojtek Kosior via
2022-10-26 19:55 ` Csepp
2022-10-27 16:59 ` Maxim Cournoyer
2022-10-27 17:28 ` Wojtek Kosior via
2022-10-28 15:38 ` Maxim Cournoyer
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=87lepjrhc9.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--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).