I'll try to explain how I use sbopkg with a custom repository.
as sbopkg can use a git repository as source, I have:
-
forked SBo's git repository (master branch);
- created a
branch for every script I modify (I find easier to manage them this way);
- merged every resulting branch
in one with all the modifications (you can avoid the previous step if you are comfortable in using directly a single branch);
- set up in /etc/sbopkg/sbopkg.conf
to use that.
you can modify the file /etc/sbopkg/repos.d/60-SBo-current.repo to point at your git repository or better create a new file (variables description is at the top of the file) with your data and configure the parameters you set there in sbopkg.conf.
as an example you can create a file /etc/sbopkg/repos.d/70-slackbuilds.repo with this content
Code:
# Repo Branch Description Tag Tool Link CheckGPG
slackbuilds master "Official git master from slackbuilds.org" custom git git://slackbuilds.org/slackbuilds.git@master ""
and then set in /etc/sbopkg/sbopkg.conf
Code:
REPO_BRANCH=${REPO_BRANCH:-master}
REPO_NAME=${REPO_NAME:-slackbuilds}
to use SlackBuilds.org's git master branch.
you should be able also to use a local repository, as described in
this mailing list message, but doing without a git repository that's useful also as a backup I personally found pretty easy to lose the changes.