https://github.com/ess/kapow
Bash package management tool
https://github.com/ess/kapow
Last synced: 3 months ago
JSON representation
Bash package management tool
- Host: GitHub
- URL: https://github.com/ess/kapow
- Owner: ess
- Created: 2010-06-03T01:28:32.000Z (about 16 years ago)
- Default Branch: master
- Last Pushed: 2010-06-02T07:20:36.000Z (about 16 years ago)
- Last Synced: 2025-02-22T21:42:13.503Z (over 1 year ago)
- Homepage:
- Size: 83 KB
- Stars: 1
- Watchers: 2
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Uh, what?
Kapow is a Bash library management tool. You might be asking yourself "WHY?"; I don't have an answer for you.
# Installation
Run the installer script:
chmod +x installer && ./installer
You'll want to open it and change the `$PREFIX` variable in case you don't like things being installed into `/usr/local`.
# Usage
If you've ever used a package manager (apt, yum, rubygems, etc., etc.), you know how to use kapow.
## Installing a new library:
kapow install [name]
## Removing a library:
kapow remove [name]
## Updating a libary:
TODO: ^ this
## Searching for libraries:
kapow search [name or partial name]
## Including the library in your script
require '[name]'
# EXAMPLES!!!??1$TEXAS
Say we have a kapow lib called 'sweet' (This assumes you have run `kapow install sweet`). The contents of sweet are as such:
sweet() {
echo "SWEEEEET"
}
Now, we want to use the 'sweet' lib inside our own script:
#!/usr/bin/env bash
require 'sweet'
sweet # echoes "SWEEEEET"
What's even more ridiculous is that after you've installed kapow, you can require libraries directly from your terminal. No joke. Try it!
# TODOS
* Write an update function
* Devise and enforce some kind of metadata in a kapow lib to pull things like creator, homepage, version, etc.
* Think of an actual use case.
# Disclaimer
Good science, you had better know what you're doing! You take full responsibility for your actions.