summary refs log tree commit diff
path: root/Cargo.lock
Commit message (Collapse)AuthorAgeFilesLines
* libsecret: 0.6.0 (private fork) -> 0.7.0 (upstream)Vika30 hours1-39/+20
| | | | libsecret is now maintained again! No need for a private fork.
* cargo update, bump minimum libadwaita version to 1.6Vika2024-12-161-148/+369
| | | | | | | | I wish there was a way to build against newer libadwaita but be able to gracefully degrade. I heard it's possible in Zig, and `libadwaita` exposes functions to query the underlying library version at runtime, so we might be able to get away with it as long as our build-time environment is new enough...
* Bump version to 1.1.0 v1.1.0Vika2024-12-031-1/+1
|
* Small tweaks for compatibility with Kittybox's inconsistent implementationVika2024-12-031-3/+3
| | | | | | I need to fix that, but that'll take a small refactor of Kittybox. I want things to work and be liberal in what I accept, so I put in some shortcuts.
* Bump version to 1.0.1 v1.0.1Vika2024-10-221-1/+1
|
* vendor libsecretVika2024-10-221-145/+54
| | | | | | | | | | | | | | | | | | | | | The libsecret-rs crate is unmaintained, so I'm vendoring it for now. Bumping the glib version turned out to be enough. The exact process I used was: 1. Cloning the repository 2. Making changes 3. `cargo build` to ensure it works 4. `cargo package --no-verify` (b/c it tries to build all crates separately instead of the entire workspace as a whole) 5. `mkdir libsecret/sys -p` 6. `tar --strip-components 1 -C libsecret -xvf ../libsecret-rs/target/package/libsecret-0.6.0.crate` 7. `tar --strip-components 1 -C libsecret/sys -xvf ../libsecret-rs/target/package/libsecret-sys-0.6.0.crate` Then `Cargo.toml` is modified to ensure the libsecret and its `-sys` crate build out of my vendored sources. In the future, if I gain maintainership of the `libsecret` crate, I could just revert this commit to make it point back to the upstream.
* cargo updateVika2024-10-221-283/+251
|
* Revert "cargo update"Vika2024-10-221-253/+285
| | | | | | | This reverts commit 94c04a70941e3b38474e7a9dcdd16cb51e4f29e0. `gettext-rs` crate released a semver-incompatible update, which breaks building.
* cargo updateVika2024-10-221-285/+253
|
* Bump version to 1.0.0 v1.0.0Vika2024-09-041-1/+1
|
* Smart Summary is now working!Vika2024-09-041-0/+1
| | | | | | | | | There's no preferences dialog, so you can't really adjust the prompt or the model it uses. The default settings work well for me. You may want to tweak them depending on your model preferences and compute budget. (Not many can afford to run Llama3-8B at high quantization. Conversely, you might have a better GPU than me and wish to run a 27B model or bigger.)
* Remove libpanel dependencyVika2024-09-041-32/+0
|
* Bring in gettext and related toolsVika2024-08-281-0/+106
| | | | xtr is better at extracting translatables from Rust than xgettext is.
* Proper main menu iconVika2024-08-251-1/+156
|
* Bump kittybox-indieauthVika2024-08-251-2/+2
|
* Send posts made in the post composerVika2024-08-201-61/+1034
|
* Initial Nix & Cargo boilerplate for a Relm4 projectVika2024-08-191-0/+1255