Conversation

Notices

1. Embed this notice
   Hélène (helene@p.helene.moe)'s status on Tuesday, 13-Sep-2022 21:38:19 JST Hélène
   considered making appimage-like releases by the way
   • Embed this notice
     tusooa :Cat_girls_Emoji_004: 西风 (tusooa@kazv.moe)'s status on Tuesday, 13-Sep-2022 21:40:07 JST tusooa :Cat_girls_Emoji_004: 西风

     in reply to
     @helene it's already appimage-like
     Hélène likes this.
   • Embed this notice
     Hélène (helene@p.helene.moe)'s status on Tuesday, 13-Sep-2022 21:40:26 JST Hélène

     in reply to

     • tusooa :Cat_girls_Emoji_004: 西风
     @tusooa not enough because it breaks on libc differences, OpenSSL and built binaries for packages
   • Embed this notice
     tusooa :Cat_girls_Emoji_004: 西风 (tusooa@kazv.moe)'s status on Tuesday, 13-Sep-2022 21:45:08 JST tusooa :Cat_girls_Emoji_004: 西风

     in reply to
     @helene appimages will fail too if you use an older libc than it was built with.
     Hélène likes this.
   • Embed this notice
     May ? (may@pl.serialmay.link)'s status on Tuesday, 13-Sep-2022 21:56:49 JST May ?

     in reply to

     • tusooa :Cat_girls_Emoji_004: 西风
     @tusooa @helene depends on what you include in the appimage, usually libc is ignored. if you really want compat you can include it though. then the only thing is fuse and the fairly generic libc-wise executable code
     Hélène likes this.