# Graphite Package Manager
**Community-driven package repository** that allows users to **create, install** packages created by **community**.









## TOC
- [Graphite Package Manager](#graphite-package-manager)
	- [TOC](#toc)









> 🚧 **Note:** Not yet implemented.









<!-- 









## Creating a Package
- Name your repo using the convention: `graphite-xyz` (where `xyz` is your package name).
- Host your package as a public GitHub repository.
- Document usage, features, and requirements clearly.
- Announce your package in GitHub Discussions or Reddit.









## Installing a Package
- Users clone the package repo and follow its installation instructions.
- Header files are typically copied to the local `gp_packages/` directory.
- Register the package in `gp_packages.txt` (locally):
	- Package name
	- Repository URL
	- Version









## Verified vs. Unverified Packages
- **Verified**: Trusted, reviewed, and stable (verification status managed by Daynlight)
- **Unverified**: Community-created; use at your own risk
- Verification status is stored locally for speed and security
- To request verification, contact Daynlight









## Updating & Removing Packages
- To update, pull the latest changes from the package repo
- To remove, delete the package files and update `gp_packages.txt`









## Best Practices
- Follow the naming convention and document your package well
- Test your package before sharing
- Engage with the community for feedback and improvements









See `Comunity.md` for more on sharing and collaborating. -->