From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id C9B6C1396D9 for ; Sun, 5 Nov 2017 15:04:40 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 433F4E0F4C; Sun, 5 Nov 2017 15:04:34 +0000 (UTC) Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 980A2E0F3F for ; Sun, 5 Nov 2017 15:04:33 +0000 (UTC) Received: from localhost ([79.223.109.98]) by mail.gmx.com (mrgmx101 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MZxch-1dphms0p27-00Lpzf for ; Sun, 05 Nov 2017 16:04:21 +0100 Date: Sun, 5 Nov 2017 16:04:20 +0100 From: tuxic@posteo.de To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] [OT] AppImage? What's that? Message-ID: <20171105150420.cug5eq2tqcomdtpt@solfire> Mail-Followup-To: gentoo-user@lists.gentoo.org References:<20171105112031.h7353gaydk3p3pel@solfire> <20171105121102.moefbq7pmkk54dxd@solfire> <20171105134857.igfmhtsksabauycb@solfire> <20ecdb6a-4ba9-7725-b485-2d3b5216d39d@gmail.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To:<20ecdb6a-4ba9-7725-b485-2d3b5216d39d@gmail.com> User-Agent: NeoMutt/20171027 Sender: X-Provags-ID: V03:K0:2ykShszNpU4p4vXKgYRDjMrvvp4X3tKoAjwsssauRYxTa0JwntQ QDPIXrsfHQLd1dmfRL3pWQR9mx2DtXiSRsGQSsprtCTvBJU7egM6VXon0LK5kYsj2y8jagf o2QiF7/Wlzf2z9FfnQfloVIa7MBIBITbUgvGge6pecT+/4reh+dRF3D3OUeWZUBlS0iqnjj 2HR55eHBoWWLti9QBgWWw== X-UI-Out-Filterresults: notjunk:1;V01:K0:EuUfYCWMLlQ=:47DyUe2bWclXjamkF5fb7A tN1tKZL4ktM11XkO3x4fqQfv30ktG8Zqh4+OZvFqHUDtL49fbFjby0vhfXufz4cByOMc9UblO i3DaB6i+LtdP3l/gcz2JWSeZnm/1McOC5XXFpmDzTkEyaOVruO00/5iXKiFJq3X6vU650EGjF UpH3vPQ7+RJ0G1wrOz8KMUa+p0CNbf0bGi4KnoDmbuF6hMppXON/4YkxLXvY3QqSikcJ1okCV xxOiuaUDm/rqRWHB4W1GF/HVSwnTZTTFK4b884XP1kz30Uxw2QN+g8nNeMejzf9F9K41f3HLF Vc5EvFvU51RKvVCF1lKMAeqMfVcDsc/7kF5Op0Czupj59FmaE8RRgjOp7QKM+Gs6+OVeHCSyC Y5Gmbc8uYTWu6TrhYPjS8iDBLxpdnIQ99+PmS3Glsfip3Oiw/zdQ33HRbtuFtKlW5aTgTEQJw sVmy6SjCEOcvrMOVgIEyPr9nhlEHEYlUM22FxZ3YaQjvQHmOvYdRergbyj8hYh46hkrwEhVyW wD7ux74A47tU120JQTC5HRqU90rzF5AwFjBj2Rq9/MUwh3eh5wgrmCPuwY78e8ZDi1J/H6hp0 UQgQ6Vu+KYRn3BzW+/PVXtZfoIVjvBcKi3TKLFHcjNIAWoidWX39MgS5mY/Fu0uRGguSVUfGL lTkTQo60o7L/vV3H34s3DT6DE6mJqgqfg/wcbYr99puInRkBLoETwMAaANjKH/gH9963UWD4+ FXjwtt89fYQDfAviH/DEXN1bjnjxZjai1jjL7fcjFDDZyt2ME2Fe2Tr2Xk0QWJAa5vqY/f1fi Nzx+O/zJGWtLb7823Ram7liZBjGCA== X-Archives-Salt: 4aa569f7-034e-43b4-bcca-fc40fc0b083a X-Archives-Hash: ef348b509e361f1fdb044ce91f524abf 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, wrote: > >>> On 11/05 06:29, Tom H wrote: > >>>> On Sun, Nov 5, 2017 at 6:20 AM, 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