Layr-Labs / Layr-Labs/devkit-cli
QoL: Add Package Manager Support Across Multiple Platforms
- Vorherrschende Sprache
- Go
- Sterne
- 27
- Forks
- 10
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Beschreibung
> NOTE: This should likely be done after the alpha phase, and definitely in multiple PRs for each package manager.
> As a QoL improvement this is a *nice to have* not a *must have*
#### Problem
Users currently need to install the EigenLayer DevKit by downloading precompiled binaries. This creates a suboptimal experience, especially for users who rely on package managers to handle dependency resolution and installation. Adding proper support across major platforms would improve accessibility, reduce onboarding friction, and align with current developer tooling conventions.
#### Solution
Create official packages for major platform package managers, including:
* Homebrew (macOS/Linux)
* Arch Linux AUR
* Debian/Ubuntu Snapcraft or Apt repository
* Fedora (DNF)
#### Motivation
This change would significantly improve the developer experience by:
1. Providing a standard way to install the EigenLayer DevKit via familiar package managers
### Expected Outcome
1. **Installation Experience**
- Users should be able to install the DevKit using their preferred package manager without significant configuration changes
```
# macOS/Linux:
$ brew install eigen-devkit
# Arch Linux:
$ yay -S eigen-devkit
```
> A good reference for how users of other linux distributions are familiar with installing third-party pacakges would be the Brave Browser installation instructions for linux: https://brave.com/linux/
2. **Documentation**
- All package installation methods must be documented in `README.md`
- The README should include a "Package Manager Installation" section
### Additional Notes
1. This feature requires maintaining multiple package definitions simultaneously
2. There should be a `contrib/` directory at the root of the repository containing all package definitions
### Implementation Approach
1. **Phase 1: Research**
- Investigate official package manager interfaces for each platform
- Create initial draft packages
2. **Phase 2: Initial Implementation**
- Write and test the package definitions
3. **Phase 3: Integration**
- Add CI workflows to build and test packages
- Update project documentation
### Resources
1. [Homebrew Formula Guide](https://docs.brew.sh/Formula-Cookbook)
2. [Arch Linux Packaging](https://wiki.archlinux.org/title/Creating_packages)
3. [Debian Packaging](https://wiki.debian.org/HowToPackageForDebian)
4. [Fedora Packaging Tutorial](https://docs.fedoraproject.org/en-US/package-maintainers/Packaging_Tutorial/)
Beitragsleitfaden
Für dieses Repository ist kein Beitragsleitfaden indexiert
Rechercherichtung
Beginne mit README.md und dem vorgeschlagenen contrib/-Verzeichnis auf Root-Ebene und prüfe anschließend die im Issue verlinkten Packaging-Referenzen für Homebrew, Arch, Debian und Fedora. Definiere den Umfang der Paketmanager-Unterstützung und wie jedes Paket das vorhandene DevKit installiert. Als abgeschlossen gilt die Arbeit, wenn Paketdefinitionen, CI-Workflows zum Erstellen und Testen dieser Pakete sowie dokumentierte Installationsmethoden in einem neuen README-Abschnitt vorhanden sind.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- arch-linux, debian, fedora, go, linux, macos, ubuntu
- Bereich
- build-system, cli, documentation, release
- Issue-Typ
- Feature
- Schwierigkeit
- 5/5
- Geschätzter Aufwand
- Über eine Woche
- Aktivitätsstatus
- Veraltet
- Klarheit
- Muss geklärt werden
- Anfängerfreundlichkeit
- 25/100