- C 96.6%
- Makefile 2.9%
- Lua 0.5%
| include | feat: pre/post install cmd support | |
| src | fix: added boot ro bind to build ans intall sandbox | |
| .gitignore | refactor: flags executed in order typed in, root now enforced | |
| awl.png | chore: tweak awl.png | |
| awlrecipe.lua | fix: awlrecipe.lua now uses install cmds | |
| LICENSE | chore: README.md + LICENSE | |
| Makefile | feat: yeah, pulling repos wasnt a good idea. made recipe search find subfolders | |
| README.md | chore: tweak read me | |
| schema.sql | feat: updating, listing packages is now implemented | |
awl - a from source package manager
license
gpl-2.0 (see https://www.gnu.org/licenses/old-licenses/gpl-2.0.txt)
compile
cd into where you cloned the repository use make to build it
make
install
after you build it use make once again to install it (with root privileges)
make install
after that runs, you probably want awl to manage itself:
awl -i awl
for some extra goodies, consider cloning the recipes repo into your .config/awl/recipes folder so you have a few packages to install:
cd ~/.config/awl/recipes
git clone https://codeberg.org/nzuum/awl-recipes
usage
awl -iurl <package(s)>
where: i -> install packages u -> update packages r -> remove packages l -> list packages
as you probably can tell, there seems to a "s -> sync repos" shaped hole in the flag list. this is by design: you are supposed to go out of your way and pull whenever you want updated recipes.
info
awl is currently very new and as such, the recipe library is not very big. this is where you get in. users are what could make or break this little project of mine. so, if you are interested, consider writing recipes for your favorite open source programs and pull request them to the recipes repo. i will take a look and accept or deny it. thanks for your attention!