<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
it is. that is why it is odd. i haven't had issues before. this
tar.gz was created slightly differently from the usual ones I
submit, to ensure correct permissions.<br>
in my project build script I have<br>
<br>
tar --mode='644' --exclude="$PKGNAME/$PKGNAME.SlackBuild" -cf
$PKGNAME.tar $PKGNAME<br>
tar --mode='755' -rf $PKGNAME.tar "$PKGNAME/$PKGNAME.SlackBuild"<br>
gzip -f $PKGNAME.tar<br>
<br>
which ensures the permissions are correct, but the resultant tar.gz
is ok. <br>
with the elilong.tar.gz in /tmp/<br>
<br>
<font face="monospace">cd /tmp/<br>
tar -xvf elilong.tar.gz gives</font><br>
<br>
<font face="monospace">tree elilong<br>
elilong<br>
├── README<br>
├── doinst.sh<br>
├── elilong.SlackBuild<br>
├── elilong.info<br>
└── slack-desc<br>
</font><br>
<br>
<div class="moz-cite-prefix">On 31/05/2026 21:54, Arnaud wrote:<br>
</div>
<blockquote type="cite"
cite="mid:DEEEF297-8D7F-4E1D-8E63-9AFD97FE2FF7@laposte.net">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="auto">The files needs to be inside a directory named by
the name of the package, here :<br>
elilong/elilong.info<br>
etc.<br>
<br>
- Yth.</div>
<div dir="auto">
<div class="k9mail-signature">-- <br>
</div>
</div>
</blockquote>
<br>
</body>
</html>