From: Tom H <tomh0665@gmail.com>
To: Gentoo User <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] [OT] AppImage? What's that?
Date: Sun, 5 Nov 2017 06:29:35 -0500 [thread overview]
Message-ID: <CAOdo=SynE-c5B7yo-gjRTKeLeq5JgOtQE7F2zp3qzjicKV=b0g@mail.gmail.com> (raw)
In-Reply-To: <20171105112031.h7353gaydk3p3pel@solfire>
On Sun, Nov 5, 2017 at 6:20 AM, <tuxic@posteo.de> wrote:
>
> I got an archive (???) of an Linux application, which
> has the extension "*.AppImage".
>
> What is that?
>
> Is it possible to "unpack" that into something more common?
> How to handle that?
Does it use this spec?
https://appimage.org/
next prev parent reply other threads:[~2017-11-05 11:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-05 11:20 [gentoo-user] [OT] AppImage? What's that? tuxic
2017-11-05 11:29 ` Tom H [this message]
2017-11-05 12:11 ` tuxic
2017-11-05 12:21 ` Tom H
2017-11-05 13:48 ` tuxic
2017-11-05 14:46 ` Alan McKinnon
2017-11-05 15:04 ` tuxic
2017-11-05 15:20 ` [gentoo-user] How to crack open an *.AppImage Was: " tuxic
2017-11-05 15:17 ` [gentoo-user] " Rich Freeman
2017-11-05 16:01 ` Peter Humphrey
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAOdo=SynE-c5B7yo-gjRTKeLeq5JgOtQE7F2zp3qzjicKV=b0g@mail.gmail.com' \
--to=tomh0665@gmail.com \
--cc=gentoo-user@lists.gentoo.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