https://github.com/bemanproject/vcpkg-registry
Science Score: 26.0%
This score indicates how likely this project is to be science-related based on various indicators:
-
○CITATION.cff file
-
✓codemeta.json file
Found codemeta.json file -
✓.zenodo.json file
Found .zenodo.json file -
○DOI references
-
○Academic publication links
-
○Academic email domains
-
○Institutional organization owner
-
○JOSS paper metadata
-
○Scientific vocabulary similarity
Low similarity (8.6%) to scientific vocabulary
Repository
Basic Info
- Host: GitHub
- Owner: bemanproject
- Language: CMake
- Default Branch: main
- Size: 27.3 KB
Statistics
- Stars: 0
- Watchers: 10
- Forks: 1
- Open Issues: 2
- Releases: 0
Metadata Files
ReadMe.md
Beman Registry
This is the Beman Project's vcpkg registry
Using the registry
The typical way to use a vcpkg registry is to add it to the package manifest, see the vcpkg documentation on manifest mode for more details. Ordinary usage of the Beman Project's registry would look like:
jsonc
{
"default-registry": { /* ... */ },
"registries": [
{
"kind": "git",
"repository": "https://github.com/bemanproject/vcpkg-registry",
"baseline": "...",
"packages": [ "beman-*" ]
}
],
"overlay-ports": [ /* ... */ ]
}
This would provide any ports prefixed with beman- from the Beman registry
when requested by a project. The Beman registry is self-sufficent and does
not rely on the vcpkg built-in registry, so can also be used directly as
a default registry if desired.
Adding / Updating a port
The Beman registry is a standard vcpkg registy, thus adding a port requires the standard steps documented in the vcpkg maintainer guide.
The Python script update_port.py handles some of the monotenous work of
updating version numbers and SHA512 hashes, and when used in conjuction with
the vcpkg x-add-version script for managing the version database can be
used to quickly update ports.
However these are presented without further commentary, it is not intended for those unfamiliar with vcpkg registry maintenance to update ports at this time.
Note for maintainers
Beman project uses it own fork of the vcpkg-cmake* host dependencies to allow
it to stand alone as a default registry. These are vendored under
beman-cmake-tools. Generally speaking these mirror the functions of
vcpkg-cmake and vcpkg-cmake-config exactly, except renamed to
beman_cmake_*.
Owner
- Name: The Beman Project
- Login: bemanproject
- Kind: organization
- Website: bemanproject.org
- Twitter: bemanproject
- Repositories: 3
- Profile: https://github.com/bemanproject
Supporting the efficient design and adoption of the highest quality C++ standard libraries
GitHub Events
Total
- Issues event: 1
- Issue comment event: 3
- Member event: 2
- Push event: 4
- Pull request review event: 1
- Pull request review comment event: 1
- Pull request event: 2
- Create event: 3
Last Year
- Issues event: 1
- Issue comment event: 3
- Member event: 2
- Push event: 4
- Pull request review event: 1
- Pull request review comment event: 1
- Pull request event: 2
- Create event: 3
Issues and Pull Requests
Last synced: 10 months ago
Dependencies
- beman-cmake-tools *