From: Efraim Flashner <efraim@flashner.co.il>
To: jbranso@dismail.de
Cc: Andy Tai <lichengtai@gmail.com>, help-guix@gnu.org
Subject: Re: guix pack and flatpak
Date: Mon, 3 May 2021 16:21:26 +0300 [thread overview]
Message-ID: <YI/41kMEPQJ6tfMM@3900XT> (raw)
In-Reply-To: <c718f6434503d67b53f49fda57b41e58@dismail.de>
[-- Attachment #1: Type: text/plain, Size: 1307 bytes --]
On Mon, May 03, 2021 at 09:14:47AM +0000, jbranso@dismail.de wrote:
> At the moment, I do not believe that it can.
>
> But it would be cool if it could...
>
> Thanks,
>
> Joshua
>
> P.S. I really probably shouldn't be responding to guix emails right now.
> I'm still working on my night audit shift, and I'm so sleepy I can barely
> write a sentence. :)
>
> May 2, 2021 7:14 PM, "Andy Tai" <lichengtai@gmail.com> wrote:
>
> > a question hopefully not too wild: Guix can generate Docker image via
> >
> > guix pack
> >
> > Only knowing flatpak in brief terms, can guix software bundle
> > mechanisms be used to create flatpak?
> >
>
I've been saving this¹ link for a while now, it shouldn't be Too Hard™
to teach 'guix pack' to export to a flatpak. I would specifically look
at the flatpak.yaml portion in the FlatpakTemplate and look through the
flatpak documentation about taking an existing directory (guix pack
--format=tarball HINT HINT) and shoving that into a flatpak.
¹ https://openbuildservice.org/2021/02/18/introducing-flatpak-builds/
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2021-05-03 13:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-02 23:13 guix pack and flatpak Andy Tai
2021-05-03 9:14 ` jbranso
2021-05-03 13:21 ` Efraim Flashner [this message]
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=YI/41kMEPQJ6tfMM@3900XT \
--to=efraim@flashner.co.il \
--cc=help-guix@gnu.org \
--cc=jbranso@dismail.de \
--cc=lichengtai@gmail.com \
/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).