To install:
$ zef install fez
fez is the command line tool used to manage your ecosystem user/pass.
as easy as: zef install fez
*** Note: if you are having trouble installing fez and you see an error referring to zlib, then please install zlib and try installing fez again prior to opening a bug.
Fez - Raku dist manager
| command | info |
|---|---|
| v|version | prints out the version of fez you're using |
| DIST MANAGEMENT | |
| init | initializes a new module |
| resource | creates a new resource file at the given path, creating the path if necessary |
| depends | add a build or runtime dependency to the meta |
| cmd | list commands this module provides |
| run | runs a command listed in cmd |
| refresh | attempts to update the META6 from the file system this does NOT prompt before overwriting |
| license | view or manage the current repo's license |
| RELEASE MANAGEMENT | |
| review | goes through the current directory to find any errors that might be lurking upon upload |
| register | registers you up for a new account |
| login | logs you in and saves your key info |
| upload | creates a distribution tarball and uploads |
| meta | update your public meta info (website, email, name) |
| reset-password | initiates a password reset using the email that you registered with |
| list | lists the dists for the currently logged in user |
| remove | removes a dist from the ecosystem (requires fully qualified dist name, copy from list if in doubt) |
| org | org actions, use fez org help for more info |
To see more information about any of these commands just run fez <cmd>, example:
~$ fez resource
Fez - Raku dist manager
USAGE
fez res <path>
fez resource <path>
Attempts to create a resource in the current dist and update the meta. Do NOT
include 'resources/' in the path, eg
fez resource usage/default
Will create the file: `resources/usage/default`.
- do I need to remove modules from cpan
- which version will zef choose if my module is also on cpan
- what's this sdist directory
No. If you want your fez modules to be prioritized then simply bump the version. Note that you can upload older versions of your modules using a tar.gz and specifing fez upload --file <path to tar.gz>.
zef will prioritize whichever gives the highest version and then the rest depends on which ecosystem is checked first which can vary system to system.
when fez bundles your source it outputs to sdist/<name>.tar.gz and then uploads that package to the ecosystem. there are two ways that fez might try to bundle your package. as of fez:ver<26+> fez will attempt to remove the sdist/ directory if no --file is manually specified
if you'd like to see your article featured here, please send a pr.
