Re: Importer (specifically rust/crates) Packaging Workflow?

[Efraim Flashner]

On Sun, Feb 23, 2025 at 10:51:27AM -0500, Andrew Wong wrote:
> Hello Guix,
> What is your workflow for adding packages via `guix import` which have a lot
> of new/updated dependencies? Though `guix import` almost always writes the
> package defs perfectly, I find the real tedium is _placing_ all of these
> imported packages in their proper places... it becomes look at
> package->judge which file it goes to->cut def->locate where it goes in the
> file alphabetically->paste, for every single package of what could be dozens
> of imported packages (sometimes it is instead an update of a package!).
> 
> 1) Is there a better way to do this?

I personally import packages one at a time.  In vim, in command mode,
':read !guix import crate foo' will insert the imported crate right at
that spot.  Then I adjust it for inheritance and grammar and such.  Once
all the packages I've added build then I go through and write a git
commit for each of them.

> 2) Is each contributor responsible for keeping the crates-*.scm (or similar)
> files sorted and if so is there an automated way to insert packages
> alphabetically?

Currently there's no way to do it automatically.

> 3) Is crates-io.scm strictly for I/O related rust packages or is it the
> de-facto "generic/xyz" file for rust?

It's named that way because the majority of the crates are registered on
the crates.io site.  Then the module became too big so we kept the
crates prefix and added the other modules.  Otherwise it would be
crates-xyz.scm.

-- 
Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

signature.asc
Description: PGP signature