From: tuxic@posteo.de
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] [OT] AppImage? What's that?
Date: Sun, 5 Nov 2017 16:04:20 +0100 [thread overview]
Message-ID: <20171105150420.cug5eq2tqcomdtpt@solfire> (raw)
In-Reply-To: <20ecdb6a-4ba9-7725-b485-2d3b5216d39d@gmail.com>
On 11/05 04:46, Alan McKinnon wrote:
> On 05/11/2017 15:48, tuxic@posteo.de wrote:
> > On 11/05 07:21, Tom H wrote:
> >> On Sun, Nov 5, 2017 at 7:11 AM, <tuxic@posteo.de> wrote:
> >>> On 11/05 06:29, Tom H wrote:
> >>>> 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/
> >>>
> >>> Dont know...
> >>> How can I unpack that to look into it?
> >>
> >> From
> >> https://github.com/AppImage/AppImageKit
> >>
> >> wget "https://github.com/AppImage/AppImageKit/releases/download/continuous/appimagetool-x86_64.AppImage"
> >> etc...
> >>
> >
> >
> > ./appimagetool-x86_64.AppImage appimagetool-x86_64.AppImage TestApp/.
> > WARNING: appstreamcli is missing, please install it if you want to use AppStream metadata
> > appimagetool-x86_64.AppImage is a file, assuming it is an AppImage and should be unpacked
> > To be implemented
> >
> > unpacking is not implemented yet.
>
>
> Reading only this thread, it looks like an upstream used a horribly
> incomplete scheme for distribution that isn't even ready for launch.
>
> And yet they distribute using it.
>
> I would be questioning why I'm using that upstream's project at all, and
> find something better by an author with more clue.
>
> Am I missing something?
>
>
> --
> Alan McKinnon
> alan.mckinnon@gmail.com
>
>
As so often, the persons 'up' in the hierarch decide things the people
'down' the hierarchy would keep their fingers off - but they will not
be asked.
I am 'down' the hierarchy and want to unpack that
archive/image/whatever.
Currently I am recompiling my kernel to support squashfs as it seems
that this image is one of that images.
If so, mounting it as an image and copying the files out of the
mountpoints directory may work.
Fingers crossed...
Cheers
Meino
next prev parent reply other threads:[~2017-11-05 15:04 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
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 [this message]
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=20171105150420.cug5eq2tqcomdtpt@solfire \
--to=tuxic@posteo.de \
--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