diff options
| author | B. Watson <urchlay@slackware.uk> | 2026-09-19 21:20:38 -0400 |
|---|---|---|
| committer | B. Watson <urchlay@slackware.uk> | 2026-09-19 21:20:38 -0400 |
| commit | b2fcc12c37b9c7eb2c43ef71e26cba976229efda (patch) | |
| tree | a0c0b6a9a73bf440ac487f4df7ee33ab702404ab /find_installed_removed | |
| parent | 60ce2c37966249d0b2a60e8811061b2641b9084f (diff) | |
| download | sbo-maintainer-tools-b2fcc12c37b9c7eb2c43ef71e26cba976229efda.tar.gz | |
find_installed_removed: clarify takeover suggestion.
Diffstat (limited to 'find_installed_removed')
| -rwxr-xr-x | find_installed_removed | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/find_installed_removed b/find_installed_removed index ec75830..a4e21ee 100755 --- a/find_installed_removed +++ b/find_installed_removed @@ -12,10 +12,10 @@ SBo site. Usually this means the builds were removed from the repo, but if you are a SBo developer, it could also find builds that you never got around to submitting to SBo. -If any removed builds are found, and they're software you actually use -and care about, you should resubmit them to SlackBuilds.org. You -can get the last version of a removed build from: -https://slackware.uk/~urchlay/boneyard/ +If any removed builds are found, and they're software you actually +use and care about, you should resubmit them to SlackBuilds.org, with +yourself as the maintainer. You can get the last version of a removed +build from: https://slackware.uk/~urchlay/boneyard/ Exit status is 0 (success) if no removed packages are installed (if there is no output), or 1 (failure) if any removed packages are |
