| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
SBo accepts updates to published packages as pull requests
(SBo-Github-Workflows.txt). Record that alongside the existing
submission-tarball route, plus the facts that took checking:
- The fork is a separate clone at ~/Programming/GIT/GITHUB/slackbuilds,
never a remote of this repo; the histories are unrelated.
- PRs are based on master. Merged PRs display a base of "github", a
transient integration branch admins retarget onto and delete, so it
is not a branch to target.
- The exported commit is synthesized at export time and uses SBo's
wording, so local history here stays independent and keeps its own
format.
|
|
Mirror SBo's own <category>/<package>/ layout instead of a flat
<package>/ one. The category is now carried by the directory, so
there's no separate map to maintain, and a package exports to the SBo
repo at the identical relative path.
misc: SecLists, exploitdb, nuclei
games: UrbanTerror
network: feroxbuster, ffuf, gobuster, metasploit-framework-bin, r8125
Categories taken from the synced SBo tree, which is authoritative.
This also repairs two things the flat layout had broken:
- test-build's category_of() returned "." for every package, since it
derives the category from the parent directory name.
- post-commit asserted a fixed depth. It now locates a build by the
directory holding the .SlackBuild, and names the archive after the
package with the package dir at the tarball root, as SBo expects.
Drops the exec bit from SecLists.SlackBuild and gobuster.SlackBuild,
flagged by sbolint once the pre-commit hook started running: SBo
requires 0644 and ships both that way.
|
|
The extract-to-tmp generator command as documented never worked on its
own. The embedded ruby has /opt/metasploit-framework baked in as its
prefix, so bundler resolves gems there regardless of the extract dir and
fails with Bundler::GemNotFound. It only appeared to work when a host
install sat at that path, which also meant it read the installed version
rather than the one being packaged.
Add the required GEM_HOME/GEM_PATH/BUNDLE_GEMFILE, note that the ruby
version in the gem path moves on upstream bumps, and drop the advice to
fall back to a live /opt install.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
|
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
|
The test-build tool and image-builder chain grew from a .extras/ helper into a
standalone toolchain, now maintained in its own repo (../sbo-dockerbuild). Remove
them here (scripts, examples, design docs) and repoint CLAUDE.md: test-building
is now done with the installed `test-build` CLI, deps resolved from the SBo tree,
both trees verified per bump. Package-maintenance files stay: nvchecker.toml,
hooks/, assets/.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
|
|
|
Add nvchecker stanzas for the seven packages moved from pentesting-suite
(SecLists, ffuf, gobuster, exploitdb, nuclei, feroxbuster,
metasploit-framework-bin) and a Build Strategies section covering Go/Rust
source builds, .deb repacks, and data packages, plus the metasploit
msfvenom-completion and man-page regeneration procedures.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
|
SBo-official packages maintained by danix, split out of my-slackbuilds.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
