[Slackbuilds-users] [RFC] a binary repack SlackBuild template.

Lockywolf for_slackbuilds-users_mlist_2023-04-21 at lockywolf.net
Tue Mar 4 06:29:30 UTC 2025


Dear SlackBuilds community,

Increasingly, we have to write more and more binary repacks,
as software is becoming harder and harder to build on the premises.

While this is an unfortunate development, and the community members
are encouraged to build software from the original sources to ensure
transparency and flexibility, sometimes building a package as a
repack is an unnecessary evil.

This message has (attached) a proposed binary-repacking SlackBuild,
which I would like to propose for an inclusion into the templates
repository.

Please comment and suggest how this template can be improved.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 227 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20250304/3fe44976/attachment.asc>
-------------- next part --------------
#!/bin/bash

# Please, name your build script ending with -bin.
# Slackware build script for <appname>-bin

# Copyright <year> <you> <where you live>
# All rights reserved.
#
# Redistribution and use of this script, with or without modification, is
# permitted provided that the following conditions are met:
#
# 1. Redistributions of this script must retain the above copyright
#    notice, this list of conditions and the following disclaimer.
#
#  THIS SOFTWARE IS PROVIDED BY THE AUTHOR "AS IS" AND ANY EXPRESS OR IMPLIED
#  WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
#  MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.  IN NO
#  EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
#  SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
#  PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
#  OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
#  WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
#  OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
#  ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

# |-----------------------------------------------------------------| #
# REMOVE THIS ENTIRE BLOCK OF TEXT #
#
# Please, name your build script ending with -bin, even if your
# hypothetical software ends with -bin by itself. So, a piece of
# software originally called frobnicate-bin would have a script name
# frobnicate-bin-bin.
#
# A license is required, and we strongly suggest you use the above
# BSD/MIT style license. We DO NOT accept "Public Domain" scripts.
# Public domain is not valid in some countries, and no license is
# worse than a "bad" license in those countries.
#
# This template is not meant to be a 'cut and paste' script to
# enable any random user to make a working package.  While
# we're certainly not discouraging use of this template, if
# you haven't manually gone through each step of the process
# without the build script (typically as a normal user, as this
# will reveal problems that you won't see as root), then there's
# a good chance that something important is missing from your
# submission.

# When using this template script, please remove as many of
# these unnecessary comments as possible.  Commented code is
# a good thing, but if it's obvious, there's no need to comment it.
#
# AGAIN, REMOVE THE COMMENTS IF THEY ARE NOT NEEDED - DON'T JUST
# DELETE THIS BLOCK OF TEXT WITHOUT BOTHERING TO READ WHAT'S IN IT.
#
# |-----------------------------------------------------------------| #

cd $(dirname $0) ; CWD=$(pwd)

PRGNAM=appname-bin			# replace with name of program
VERSION=${VERSION:-1.4.1}	# replace with version of program
BUILD=${BUILD:-1}
TAG=${TAG:-_SBo}		# the "_SBo" is required
PKGTYPE=${PKGTYPE:-tgz}

TARNAM=appname

# Automatically determine the architecture we're building on:
if [ -z "$ARCH" ]; then
  case "$( uname -m )" in
    i?86) ARCH=i586 ;;
    arm*) ARCH=arm ;;
    # Unless $ARCH is already set, use uname -m for all other archs:
       *) ARCH=$( uname -m ) ;;
  esac
fi

# If the variable PRINT_PACKAGE_NAME is set, then this script will report what
# the name of the created package would be, and then exit. This information
# could be useful to other scripts.
if [ ! -z "${PRINT_PACKAGE_NAME}" ]; then
  echo "$PRGNAM-$VERSION-$ARCH-$BUILD$TAG.$PKGTYPE"
  exit 0
fi

TMP=${TMP:-/tmp/SBo}	# For consistency's sake, use this
PKG=$TMP/package-$PRGNAM
OUTPUT=${OUTPUT:-/tmp}	# Drop the package in /tmp

if [ "$ARCH" = "i586" ]; then
  LIBDIRSUFFIX=""
  UNSUP=1
elif [ "$ARCH" = "i686" ]; then
  LIBDIRSUFFIX=""
  UNSUP=1
elif [ "$ARCH" = "x86_64" ]; then
  LIBDIRSUFFIX="64"
elif [ "$ARCH" = "aarch64" ]; then
  LIBDIRSUFFIX="64"
  UNSUP=1
else
  LIBDIRSUFFIX=""
  UNSUP=1
fi

if [[ "$UNSUP" == 1 ]] ; then
  printf "Unsupported architecture: unknown.\n" 1>&2
fi

# If your package is actually "noarch", uncomment the following line.
#ARCH=noarch

set -e # Exit on most errors
# If you prefer to do selective error checking with
#   command || exit 1
# then that's also acceptable.

rm -rf $PKG
mkdir -p $TMP $PKG $OUTPUT
cd $TMP
rm -rf $TARNAM-$VERSION
tar xvf $CWD/$TARNAM-$VERSION-$ARCH.tar.gz
cd $TARNAM-$VERSION

chown -R root:root .
find -L . \
 \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 \
  -o -perm 511 \) -exec chmod 755 {} + -o \
 \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \
  -o -perm 440 -o -perm 400 \) -exec chmod 644 {} +

# Unpack the archive to /opt/
install -d -m755 $PKG/opt
mv ${TARNAM}-${VERSION}-${ARCH} $PKG/opt

# Make a binary softlink. You might want to make a shell script instead,
# see your own particular use-case.
# You especially might want to do it if you need to UNSET some environment
# variable. Java is particularly prone to this, many binary repacks
# have to unset _JAVA_OPTIONS
mkdir -p "$PKG"/usr/bin
(
    cd $PKG/usr/bin
    ln -sr ../../opt/${TARNAM}-${VERSION}-${ARCH}/${PRGNAM} ./
)

PKGOPT=$PKG/opt/${TARNAM}-${VERSION}-${ARCH}

# You may have to install something into /usr/lib$LIBDIRSUFFIX , it is hard to
# guess. See for yourself. Browser plugins, cmake or pkg-config scripts.
# install -Dm644 $PKGOPT/plugins/ $PKG/usr/lib$LIBDIRSUFFIX/mozilla/plugins

# Install desktop file
install -Dm644 $PKGOPT/$TARNAM.desktop \
        $PKG/usr/share/applications/$TARNAM.desktop

# Install icons
install -Dm644 $PKGOPT/images/$TARNAM.svg \
        $PKG/usr/share/icons/hicolor/scalable/$TARNAM.svg
install -Dm644 $PKGOPT/images/$TARNAM.svg \
        $PKG/usr/share/pixmaps/$TARNAM.svg


# Copy program documentation into the package
# The included documentation varies from one application to another, so be sure
# to adjust your script as needed
# Also, include the SlackBuild script in the documentation directory
mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION
cp -a \
  <documentation> \
  $PKG/usr/doc/$PRGNAM-$VERSION
cat $CWD/$PRGNAM.SlackBuild > $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild

# Copy the slack-desc (and a custom doinst.sh if necessary) into ./install
mkdir -p $PKG/install
cat $CWD/slack-desc > $PKG/install/slack-desc
cat $CWD/doinst.sh > $PKG/install/doinst.sh

# Final sanity check.
if [[ "${PRGNAM: -4}" != "-bin" ]] ; then
  printf "Fatal Error: PRGNAM must end in '-bin', but now ends with %s\n" \
         "${PRGNAM: -4}"
  exit 2
fi

# Make the package; be sure to leave it in $OUTPUT
# If package symlinks need to be created during install *before*
# your custom contents of doinst.sh runs, then add the -p switch to
# the makepkg command below -- see makepkg(8) for details
cd $PKG
/sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$VERSION-$ARCH-$BUILD$TAG.$PKGTYPE
-------------- next part --------------


-- 
Your sincerely,
Vladimir Nikishkin (MiEr, lockywolf)
(Laptop)


More information about the SlackBuilds-users mailing list