SLACKWARE64-CURRENT · ONE QEMU VMThe package buildsystemHow a SlackBuild becomes a published package, in the order a build happens.1▤Assemble the repoSLACKREPO_SETUPMY TOOLWeekly: clone Ponce's SBo current, overlay my-slackbuilds +Slackware-Pentesting-Suite as subtrees, shadow duplicates.2◈Fix -current depsMKHINT -FMY TOOLSweep the tree and write DELREQUIRES hints for phantomdeps that -current already ships.3⚙BuildSLACKREPOUPSTREAMCompile each package + deps in a clean chroot, track gitrevisions to rebuild only what moved.4☁PublishFINISH HOOKS + REPO-HTML-STRUCTUREMY TOOLRegenerate slackpkg+ metadata, build the themed HTMLfrontend, rsync live to packages.danix.xyz, notify.Test on 15.0 stableSBO-BATCH-TESTERMY TOOLFor my own SBo-bound packages only: build in a disposable overlaychroot over clean Slackware 15.0 to catch current-vs-stable drift.↳ BEFORE SBo SUBMIT · SIDE PATH (does not gate the main pipeline)↻ Weekly cycle: reassemble → fix deps → build → publish, with a 15.0 spot-test for anything headed upstream.