| 1 |
On 11/05 04:04, tuxic@××××××.de wrote: |
| 2 |
> On 11/05 04:46, Alan McKinnon wrote: |
| 3 |
> > On 05/11/2017 15:48, tuxic@××××××.de wrote: |
| 4 |
> > > On 11/05 07:21, Tom H wrote: |
| 5 |
> > >> On Sun, Nov 5, 2017 at 7:11 AM, <tuxic@××××××.de> wrote: |
| 6 |
> > >>> On 11/05 06:29, Tom H wrote: |
| 7 |
> > >>>> On Sun, Nov 5, 2017 at 6:20 AM, <tuxic@××××××.de> wrote: |
| 8 |
> > >>>>> |
| 9 |
> > >>>>> I got an archive (???) of an Linux application, which |
| 10 |
> > >>>>> has the extension "*.AppImage". |
| 11 |
> > >>>>> |
| 12 |
> > >>>>> What is that? |
| 13 |
> > >>>>> |
| 14 |
> > >>>>> Is it possible to "unpack" that into something more common? |
| 15 |
> > >>>>> How to handle that? |
| 16 |
> > >>>> |
| 17 |
> > >>>> Does it use this spec? |
| 18 |
> > >>>> |
| 19 |
> > >>>> https://appimage.org/ |
| 20 |
> > >>> |
| 21 |
> > >>> Dont know... |
| 22 |
> > >>> How can I unpack that to look into it? |
| 23 |
> > >> |
| 24 |
> > >> From |
| 25 |
> > >> https://github.com/AppImage/AppImageKit |
| 26 |
> > >> |
| 27 |
> > >> wget "https://github.com/AppImage/AppImageKit/releases/download/continuous/appimagetool-x86_64.AppImage" |
| 28 |
> > >> etc... |
| 29 |
> > >> |
| 30 |
> > > |
| 31 |
> > > |
| 32 |
> > > ./appimagetool-x86_64.AppImage appimagetool-x86_64.AppImage TestApp/. |
| 33 |
> > > WARNING: appstreamcli is missing, please install it if you want to use AppStream metadata |
| 34 |
> > > appimagetool-x86_64.AppImage is a file, assuming it is an AppImage and should be unpacked |
| 35 |
> > > To be implemented |
| 36 |
> > > |
| 37 |
> > > unpacking is not implemented yet. |
| 38 |
> > |
| 39 |
> > |
| 40 |
> > Reading only this thread, it looks like an upstream used a horribly |
| 41 |
> > incomplete scheme for distribution that isn't even ready for launch. |
| 42 |
> > |
| 43 |
> > And yet they distribute using it. |
| 44 |
> > |
| 45 |
> > I would be questioning why I'm using that upstream's project at all, and |
| 46 |
> > find something better by an author with more clue. |
| 47 |
> > |
| 48 |
> > Am I missing something? |
| 49 |
> > |
| 50 |
> > |
| 51 |
> > -- |
| 52 |
> > Alan McKinnon |
| 53 |
> > alan.mckinnon@×××××.com |
| 54 |
> > |
| 55 |
> > |
| 56 |
> |
| 57 |
> As so often, the persons 'up' in the hierarch decide things the people |
| 58 |
> 'down' the hierarchy would keep their fingers off - but they will not |
| 59 |
> be asked. |
| 60 |
> |
| 61 |
> I am 'down' the hierarchy and want to unpack that |
| 62 |
> archive/image/whatever. |
| 63 |
> |
| 64 |
> Currently I am recompiling my kernel to support squashfs as it seems |
| 65 |
> that this image is one of that images. |
| 66 |
> If so, mounting it as an image and copying the files out of the |
| 67 |
> mountpoints directory may work. |
| 68 |
> |
| 69 |
> Fingers crossed... |
| 70 |
> |
| 71 |
> Cheers |
| 72 |
> Meino |
| 73 |
> |
| 74 |
> |
| 75 |
|
| 76 |
OK, I have found a way -- for all hesitating with this |
| 77 |
closed-opensource AppImage-blobs: |
| 78 |
|
| 79 |
chmod file.AppImage |
| 80 |
./file.AppImage # wait ... |
| 81 |
mount # find mount point of this sealed bag,,,mine was /tmp/.mount-someting |
| 82 |
cp -a /tmp/.mount-something ~/somesaveplace |
| 83 |
<quit the application started by file.AppImage here> |
| 84 |
|
| 85 |
That's it. |
| 86 |
Happy tinkering! |
| 87 |
|
| 88 |
Cheers |
| 89 |
Meino |
Archives