Create another repo to make a "module manager." The base module manager should use libgit2 to pull remote git repos to disk that are suspected nibi modules. Using libnibi we can ensure its a valid module and run tests against it.
When we clone the repos we have to see if they require a build step as they might be a c++ based module, this means we may need a standardized "build" file using toml or something so the manager can know how to build the thing.
Eventually we would like to update the module manager to be able to curl tar or zip files for installs as well so we don't need to rely on git and doing builds every time a module is installed.
Create another repo to make a "module manager." The base module manager should use libgit2 to pull remote git repos to disk that are suspected nibi modules. Using libnibi we can ensure its a valid module and run tests against it.
When we clone the repos we have to see if they require a build step as they might be a c++ based module, this means we may need a standardized "build" file using toml or something so the manager can know how to build the thing.
Eventually we would like to update the module manager to be able to curl tar or zip files for installs as well so we don't need to rely on git and doing builds every time a module is installed.