No description
Find a file
2025-01-23 17:41:33 +01:00
.vscode initial commit 2024-08-16 19:54:49 +02:00
assets aaaa: commit worktree 2025-01-22 02:02:27 +01:00
build-aux aaaa: commit worktree 2025-01-22 02:02:27 +01:00
libpaket aaaa: commit worktree 2025-01-22 02:02:27 +01:00
paket-utils aaaa: commit worktree 2025-01-22 02:02:27 +01:00
po aaaa: commit worktree 2025-01-22 02:02:27 +01:00
src aaaa: commit worktree 2025-01-22 02:02:27 +01:00
.gitignore chore: git: ignore result symlink created by nix 2024-08-28 15:47:16 +02:00
build.rs aaaa: commit worktree 2025-01-22 02:02:27 +01:00
Cargo.lock aaaa: commit worktree 2025-01-22 02:02:27 +01:00
Cargo.toml aaaa: commit worktree 2025-01-22 02:02:27 +01:00
default.nix aaaa: commit worktree 2025-01-22 02:02:27 +01:00
LICENSE chore: add licese file 2024-08-16 19:56:12 +02:00
meson.build aaaa: commit worktree 2025-01-22 02:02:27 +01:00
meson_options.txt aaaa: commit worktree 2025-01-22 02:02:27 +01:00
paket.gresource.xml fix: colorize search button correctly 2025-01-23 17:41:33 +01:00
README.md aaaa: commit worktree 2025-01-22 02:02:27 +01:00

paket

Files and influences from other projects

  • i18n.rs and build-aux/{checks,dist-vendor}.sh are directly copied from amberol
  • src/lib.rs has code from amberol for initalizing gettext
  • paket-utils/src/lib.rs system_get_accept_languages is 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 auditable and 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-meson as an wrapper to meson setup to 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%.