Is there an official SBo HOWTO on setting up a clean chroot for working with buildscripts?
by FlinchX from LinuxQuestions.org on (#4Z37Z)
While reading the SBo mailing list, I randomly see replies like "I've tried the buildscript in a clean chroot and I can (or I can't) reproduce issue X".
End users just download SBo buildscripts, execute them (as root) on their systems and install the resulting packages - either by hand or by automating the process using a tool like sbopkg.
As I understand, the development/debug process of the buildscripts that end being submitted to SBo and get added to the repository, is slightly different. While it is possible to do it on a regular Slackware system, I believe the recommended way is to do it on a fully patched latest stable Slackware with no additional third party packages installed. This helps at least correctly finding out all third party dependencies that do not belong to vanilla Slackware and ensures that the package builds on a system with default settings.
Now, while there are multiple documentation sources about writing buildscripts and the official SBo repository for buildscript templates, I can't seem to find any HOWTO documenting the workflow of setting up said clean chroot "sandbox". I can't seem to find anything in the SBo FAQ either.
Is there such a HOWTO about setting up a clean chroot for developing a buildscript inside it? One that is SBo-centric and complements the SBo buildscript templates (because I believe AlienBOB does things slightly differently and his work ends in his own repository rather than SBo).
End users just download SBo buildscripts, execute them (as root) on their systems and install the resulting packages - either by hand or by automating the process using a tool like sbopkg.
As I understand, the development/debug process of the buildscripts that end being submitted to SBo and get added to the repository, is slightly different. While it is possible to do it on a regular Slackware system, I believe the recommended way is to do it on a fully patched latest stable Slackware with no additional third party packages installed. This helps at least correctly finding out all third party dependencies that do not belong to vanilla Slackware and ensures that the package builds on a system with default settings.
Now, while there are multiple documentation sources about writing buildscripts and the official SBo repository for buildscript templates, I can't seem to find any HOWTO documenting the workflow of setting up said clean chroot "sandbox". I can't seem to find anything in the SBo FAQ either.
Is there such a HOWTO about setting up a clean chroot for developing a buildscript inside it? One that is SBo-centric and complements the SBo buildscript templates (because I believe AlienBOB does things slightly differently and his work ends in his own repository rather than SBo).