crmne/native-packages
crmne/native-packages has 39 GitHub stars and 1 forks. GitHot measured 0 stars in 24 hours, +1 in 7 days, and +1 in 15 days. Last checked 2026-11-20 07:40 UTC. Last push 2026-11-16.
可以做什么
- Linux - DEB, RPM, AppImage, Flatpak bundles, snaps, Arch Linux packages, Alpine APK, IPK, and source RPM
- macOS - DMG, using your packaging script; optional Apple signing and notarization
- Windows - MSIX, or MSI and Inno Setup installers using your packaging script; optional Azure Artifact Signing
实测星标增长
- 24小时
- 0
- 7天
- +1
- 15天
- +1
- 1个月
- 正在收集历史
各周期内的星标净变化,周期相互重叠,并非每日新增。缺失的测量保持空白。星标代表关注度,不代表软件质量。
关于
Turn your built app into Linux packages, macOS disk images, and Windows installers. Publish releases and update distribution recipes from one YAML file.
开发工具README.md
原文
native-packages
Turn your built application into packages people can install.
Describe your app's files and supported platforms in one YAML file. Then build Linux packages, macOS disk images, or Windows installers, upload them to a GitHub release, and update distribution recipes such as AUR packages and Homebrew casks.
You bring the compiled app. native-packages handles packaging and release updates.
https://github.com/user-attachments/assets/e3157514-570d-47b3-a2e9-aca70042a138
Get started
Install with Ruby 3.2 or later:
gem install native-packages
From your application directory, create a configuration:
native-packages init --interactive
The setup creates native-packages.yaml with a Linux x86-64 starting point.
Review the app's metadata, the path to your compiled files, and the package
formats you want. The getting started guide
walks through a complete example and the required packaging tools.
Check your setup and build:
native-packages doctor
native-packages build --version 1.2.3
Your packages are in dist/packages/1.2.3/, together with checksums and a build
record. Local builds work without a GitHub release or credentials.
What can I build?
| Platform | Outputs |
|---|---|
| Linux | DEB, RPM, AppImage, Flatpak bundles, snaps, Arch Linux packages, Alpine APK, IPK, and source RPM |
| macOS | DMG, using your packaging script; optional Apple signing and notarization |
| Windows | MSIX, or MSI and Inno Setup installers using your packaging script; optional Azure Artifact Signing |
Each target needs files built for that platform. DMG builds run on macOS; MSI and Inno builds run on Windows. See supported platforms for prerequisites and distribution recipes.
Guides
Start with getting started.
- Building packages — add files, dependencies, and more targets.
- Publishing a release — build from release assets and upload packages.
- GitHub Actions — add packaging to your release workflow.
- macOS and Windows installers — connect your native packaging scripts.
- Apple signing and notarization — prepare macOS downloads for distribution.
- Windows code signing: sign Windows executables and installers with Azure Artifact Signing.
- Release signatures and attestations: authorize updater downloads and identify their build workflow.
- Hosted package repositories: publish signed repositories that users update through their package manager.
- AUR, Homebrew, and other repositories — generate and publish recipes.
- Omarchy packages: write a first Omarchy recipe that Omarchy's bot then keeps updated.
For a particular option or error, see the configuration reference, command reference, and troubleshooting guide.
Contributing
See Contributing for development, tests, and running the
documentation site locally. Upgrading an older setup? Read
the migrate command reference.