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.
in my project build script I have
tar --mode='644' --exclude="$PKGNAME/$PKGNAME.SlackBuild" -cf
$PKGNAME.tar $PKGNAME
tar --mode='755' -rf $PKGNAME.tar "$PKGNAME/$PKGNAME.SlackBuild"
gzip -f $PKGNAME.tar
which ensures the permissions are correct, but the resultant tar.gz is ok.
with the elilong.tar.gz in /tmp/
cd /tmp/
tar -xvf elilong.tar.gz gives
tree elilong
elilong
├── README
├── doinst.sh
├── elilong.SlackBuild
├── elilong.info
└── slack-desc
On 31/05/2026 21:54, Arnaud wrote:
The files needs to be inside a directory named by the name of the
package, here :
elilong/elilong.info
etc.
- Yth.
--
_______________________________________________
SlackBuilds-users mailing list
[email protected]
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/
