Skip to content
generated from vpkg-project/registry

Template to use when creating a package registry for vpkg.

Notifications You must be signed in to change notification settings

vpkg-project/registry-template

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

3 Commits
 
 
 
 
 
 

Repository files navigation

vpkg Registry

The official package listing/registry repository for vpkg, an alternative package manager for V.

Adding packages to the list

To add packages, simply fork this repository, edit registry.json, and create a pull request.

registry.json

registry.json is a JSON file containing an array of objects. Each package object should have the following fields.

  • name - Name of the package
  • url - URL to be used to retrieve the package.
  • method - The method of download of downloading the package. (vpkg supports git, hg, and svn)

Requirements

In order for your pull request to have more chances of getting accepted into the registry, your package must be compliant with the set of rules listed below:

  • It must be tested on the latest version of V.

Including package manifest files (like v.mod and vpkg.json) into the modules/package are optional but is highly recommended if your packages include additional dependencies as well as additional metadata like version number in order for better tracking/updating of packages.

Updating package information

There are some cases wherein a package gets updated (e.g renaming a package name) for various reasons. And updating it has the same process as submitting a package to the registry. However, the new information must not be in conflict with other packages so be sure to verify it before submitting.

We high encourage to finalize everything before submitting it to the registry to avoid unnecessary edits.

About

Template to use when creating a package registry for vpkg.

Topics

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages