options=(!strip)
to your PKGBUILD. Not sure if having a PKGBUILD for an AppImage makes sense, though. After all the idea of an AppImage is that the user can just run it, no need to install.
For actual installed software it would be better to place it properly in the file system, no need to have the entire AppImage squashfs. If the software is also available in other formats (source, binary archive) I would look into packaging this. If not, extracting the AppImage and collecting the files from there might be another option.
Related discussion: https://bbs.archlinux.org/viewtopic.php?id=233510
]]>As to you actual question, the size difference is due to makepkg stripping binaries. If you run `strip` on the original binary, you will see it's size drop drastically.
Note, there are also many other problems with this PKGBUILD that need to be fixed before it could be submitted.
]]>pkgname=github-desktop
pkgver=1.0.4_beta0
pkgrel=1
arch=('x86_64')
url="https://github.com/gengjiawen/desktop/releases"
source=('github-desktop.desktop')
sha256sums=(
'SKIP')
prepare() {
wget https://github.com/gengjiawen/desktop/releases/download/v1.0.4-beta0/desktop-1.0.4-beta0-x86_64.AppImage -O ${pkgname}.AppImage
chmod +x ${pkgname}.AppImage
}
package() {
mkdir -p "${pkgdir}"/usr/{bin,share/applications}
cp ${srcdir}/${pkgname}.desktop ${pkgdir}/usr/share/applications
cp ${srcdir}/${pkgname}.AppImage ${pkgdir}/usr/bin/${pkgname}
#mv ${pkgdir}/usr/bin/${pkgname}.AppImage ${pkgdir}/usr/bin/${pkgname}
}
Furthermore if I try to copy it outside of $pkgdir the resulting file is created correctly without issues.
Someone know why this happen?
Regard rez23