tar -xzf bbtoolsflver-*.tar.gz cd bbtoolsflver/ cat version.txt | grep FILTER_VER Expected output: FILTER_VER=bbtools_fl_2.1 SDMs require structured packages ( .deb , .rpm , or .msi ). If you only have the source tarball, you must convert it. Option A: Convert to .deb (For APT-based SDM) Use checkinstall or create a manual DEB structure.
chmod +x /usr/local/bin/bbtoolsflver-sdm Now, within your SDM workflow, call: bbtoolsflver to sdm install
# Using WiX: heat directory, candle, light heat dir bbtoolsflver -gg -sfrag -out bbtoolsflver.wxs candle bbtoolsflver.wxs light bbtoolsflver.wixobj -o bbtoolsflver.msi # Import MSI into SCCM as an Application. The key challenge with bbtoolsflver is ensuring SDM recognizes the filter flag when calling BBTools. tar -xzf bbtoolsflver-*
sudo apt install checkinstall cd bbtoolsflver/ # Create a custom install script mkdir -p debian/DEBIAN cat > debian/DEBIAN/control << EOF Package: bbtoolsflver Version: 1.0.0 Section: science Priority: optional Architecture: amd64 Depends: openjdk-11-jre-headless Description: BBTools with filter version flver for SDM EOF mkdir -p debian/usr/local/bbtoolsflver cp -r * debian/usr/local/bbtoolsflver/ Build DEB dpkg-deb --build debian bbtoolsflver_1.0.0_amd64.deb Deploy via SDM sudo dpkg -i bbtoolsflver_1.0.0_amd64.deb Option B: Convert to .rpm (For YUM/DNF SDM) Use fpm (Effing Package Management) to simplify the conversion. chmod +x /usr/local/bin/bbtoolsflver-sdm Now