No description
| .forgejo/workflows | ||
| .vscode | ||
| assets | ||
| build-aux | ||
| libpaket | ||
| paket-utils | ||
| po | ||
| src | ||
| .gitignore | ||
| build.rs | ||
| Cargo.lock | ||
| Cargo.toml | ||
| default.nix | ||
| LICENSE | ||
| meson.build | ||
| meson_options.txt | ||
| paket.gresource.xml | ||
| README.md | ||
paket
Files and influences from other projects
i18n.rsandbuild-aux/{checks,dist-vendor}.share directly copied from amberolsrc/lib.rshas code from amberol for initalizing gettextpaket-utils/src/lib.rssystem_get_accept_languagesis based on libsoup3 and GNOME Web- the Relm4 book, libadwaita docs and so much more
This project is standing upon of the shoulders of giants. I'm sorry if missed something here. I want to give proper attribution, please open an issue. Especially if I violated a copyright license by publishing it.
How to run
If you're a dev
Use cargo run, meson devenv is not supported (yet, merge requests are welcome).
If you're a package maintainer
I don't recommend publishing this software in conventional stable releases, I want people to use the latest version due to the volatile nature of a reverse engineering project. An exception is NixOS, even though the quality of many packages are lacking there, people can easily mixin nixpkgs-unstable to receive the latest version.
If you want to package it:
- wait for a release
- make sure dependencies are met,
cargo auditableand the ones in./meson.build - do to usual meson dance (
setup,compile,install). you're distro has probably an abstraction for meson packages, use that if possible.- e.g. Alpine Linux has
abuild-mesonas an wrapper tomeson setupto apply distro defaults for a release - if you're distro doesn't have support for meson, then don't package this. please. i will write code that breaks running on you're system if you screw up packaging. this comment reflects my opinion to 100%.
- e.g. Alpine Linux has