summaryrefslogtreecommitdiffstats
path: root/pkgs/tools/graphics/svgbob
AgeCommit message (Collapse)Author
2024-07-14fetchCrate: sha256 -> hashPyrox
Should cause no rebuilds, as this is just updating attributes.
2024-04-28treewide: adopt orphaned packagesChristina Sørensen
Signed-off-by: Christina Sørensen <christina@cafkafk.com>
2024-04-24maintainers: drop marsamMario Rodas
2023-11-23treewide: add mainProgramh7x4
2023-08-30svgbob: 0.7.0 -> 0.7.2R. Ryantm
2023-04-15svgbob: add changelog to metaMario Rodas
2023-04-15svgbob: 0.6.6 -> 0.7.0Mario Rodas
https://github.com/ivanceras/svgbob/raw/0.7.0/Changelog.md
2022-02-28svgbob: 0.6.5 -> 0.6.6R. Ryantm
2022-02-20svgbob: 0.6.4 -> 0.6.5Mario Rodas
2022-02-20svgbob: 0.6.3 -> 0.6.4R. Ryantm
2022-02-10svgbob: 0.6.2 -> 0.6.3R. Ryantm
2021-09-22svgbob: 0.5.4 -> 0.6.2R. RyanTM
2021-08-15svgbob: 0.5.3 -> 0.5.4Mario Rodas
2021-07-15svgbob: 0.4.2 -> 0.5.3Mario Rodas
2021-05-08treewide: fix cargoSha256/cargoHashDaniël de Kok
Rust 1.50.0 incorporated a Cargo change (rust-lang/cargo#8937) in which cargo vendor erroneously changed permissions of vendored crates. This was fixed in Rust 1.51.0 (rust-lang/cargo#9131). Unfortunately, this means that all cargoSha256/cargoHashes produced during the Rust 1.50.0 cycle are potentially broken. This change updates cargoSha256/cargoHash tree-wide. Fixes #121994.
2020-09-20svgbob: fix buildRobert Scott
loosen lint settings
2020-08-16buildRustPackage: remove platform.all from packageszowoq
2020-03-08svgbob: upgrade cargo fetcher and cargoSha256Benjamin Hipple
2020-02-13treewide: change fetchCargoTarball default to opt-outBenjamin Hipple
Changes the default fetcher in the Rust Platform to be the newer `fetchCargoTarball`, and changes every application using the current default to instead opt out. This commit does not change any hashes or cause any rebuilds. Once integrated, we will start deleting the opt-outs and recomputing hashes. See #79975 for details.
2019-10-01svgbob: fix buildMaximilian Bosch
See https://hydra.nixos.org/build/102480738 Bumping to latest version (which is 0.4.2 according to Cargo.lock) fixes the build error. As no dependency changes happened, cargoSha256 doesn't need to be updated. ZHF #68361
2019-06-11svgbob: init at 2018-10-05Mario Rodas