Packaging the app
This page is intended for individuals who wish to redistribute or package Beaver for package managers and platforms not yet supported. It is not intended for packaging releases of the app its
Last updated
This page is intended for individuals who wish to redistribute or package Beaver for package managers and platforms not yet supported. It is not intended for packaging releases of the app its
Last updated
The packaging library electron-builder doesn't support flatpaks to learn more visit
A good example of how this guide should be used, even though it wasn't created using this guide, is the by a wonderful member of our community.
Let's suppose you are here to package Beaver Notes for your favorite package manager, whether it's for ๐งLinux, ๐macOS, or ๐ชWindows. The first thing you should do is check the package manager's website or repository for a documentation page. This will help you cover the steps we can't provide here due to the variety of package managers.
Usually you'll need the following to package an app:
Knowledge of the Language used by the package manager
The SHA256 of the original package or source code
You can get the SHA256 either from or by running the following command in your terminal or Powershell.
๐ชWindows
๐ง Linux / ๐ macOs
The following piece of code is an example of how a typical package manager manifest looks. Please note that this may vary from one package manager to another and is provided here for illustrative purposes only.
That's it you know known what you need to package Beaver Notes for your favorite repo.