The slope language package manager
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
sloum f6856766bf Makes sure that the import name matches the module title, rather than the remote repo path 1 month ago
operators Makes sure that the import name matches the module title, rather than the remote repo path 1 month ago
.gitignore Adds man page and makefile, updates license, removes binary 2 months ago
LICENSE Adds man page and makefile, updates license, removes binary 2 months ago
Makefile Adds man page and makefile, updates license, removes binary 2 months ago
README.md Updates slp to have a more normalized syntax and updates surrounding documentation 1 month ago
TODO.md Fix < and > in TODO 4 years ago
go.mod Initial commit of pluto-lang plp fork 2 months ago
go.sum Initial commit of pluto-lang plp fork 2 months ago
main.go Makes sure that the import name matches the module title, rather than the remote repo path 1 month ago
slp.1 Updates slp to have a more normalized syntax and updates surrounding documentation 1 month ago

README.md

slp

SLope Package manager.

An easy way to install, remove, and update slope packages.

slp docs    [module]      # open a module's readme in $PAGER
slp gen                   # creates new module dir/skeleton
slp help                  # print usage information
slp install [module...]	  # installs module(s)
slp installed             # lists all installed packages
slp list                  # lists all available packages
slp remove 	[module...]   # removes module(s)
slp search  [term...]     # searches for modules
slp show    [module...]   # shows details module(s)
slp update  [module...]   # updates module(s)

Packages can be registered in the repository at https://git.rawtext.club/slope-lang/packages by submitting a PR to that repository

A note on module versioning: At present, slp does not handle any versioning and will always grab the newest version of a module, while update will always update to the newest. There are plans in place to declare a module release via the release's tag value: module-name@tag (ex. ini@0.2.1). Stay tuned for an announcement that that has been added. In the meantime: good fortune and safe journeys in the wilderness.