Hello, Rutherther <[email protected]> writes:
> Hi Tomas, > > Tomas Volf <[email protected]> writes: > >> Hello, >> >> I am trying to package cbindgen-0.29.2 for certain Guix channel, but it > > First of all recently there have been some work from Ian, here > <https://codeberg.org/guix/guix/pulls/4804/commits/0ab7d68d0534c02c9c7f633330378a68afa4c9c2>, > packaging cbindgen 0.29. So you could also just use that if you > wanted. Thank you for the pointer. With the next upgrade, I will switch to Ian's package, but I did not want to wait for it to be merged -- every Firefox release fixes a lot of CVEs. (And of course my thanks to Ian for doing the work!) > >> is first time trying to use the new approach to the rust-based >> application, so I am unsure is this supposed to be done "correctly". > > I would say the correct intended way is to let this all get handled > by the importer, the same way when you're creating a package, updating > the package etc. Really there shouldn't be much need to deal > with Cargo dependencies by hand. The only unsupported scenario is > workspace git dependencies, where you indeed do have to do something manually. > > Use the etc/teams/rust/rust-crates.tmpl from Guix for rust crates file > in your channel and then follow the > https://guix.gnu.org/cookbook/en/html_node/Common-Workflow-for-Rust-Packaging.html> > rust packaging workflow, replacing the bits with your own rust crates > file and the package you desire. lookup-cargo-inputs accepts a module to > use for the rust crates. Looking at the mentioned node in the manual, it seems like that would duplicate lot of effort already put into packaging the crates in Guix. It is great that the tooling accounts for being able to put the generated modules into a specific file, same with lookup-cargo-inputs. Though I admit I hoped for a way to reuse already existing crates. Tomas -- There are only two hard things in Computer Science: cache invalidation, naming things and off-by-one errors.
signature.asc
Description: PGP signature
