unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: Martin Becze <mjbecze@riseup.net>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Rust packaging coordination
Date: Sun, 19 Jan 2020 12:09:32 +0200	[thread overview]
Message-ID: <20200119100932.GC1603@E5400> (raw)
In-Reply-To: <3a961774-e715-444a-a4e1-dcaf01ee202d@riseup.net>

[-- Attachment #1: Type: text/plain, Size: 1647 bytes --]

On Sat, Jan 18, 2020 at 11:48:12AM -0500, Martin Becze wrote:
> I have packaged alacritty (im using it as a test app for the recursive crate
> importer). I'll wait until you get tokei in!
> 
> On 1/16/20 3:14 AM, John Soo wrote:
> > Hello guix and rust packagers,
> > 
> > I’m curious if anyone else is working on packaging rust apps.  I have been working on a patch set for tokei and it’s getting close to done.
> > 
> > I would not like it if I had to rebase all 50 patches and I wouldn’t want anyone else to have to rebase theirs. So if you are working on any rust packages, maybe we should coordinate to make it less painful to merge.
> > 
> > Thanks!
> > 
> > John
> > 
> 

I want to remind everyone of a couple of things with rust packages:
* packages get added in alphabetical order
* every package is rust-foo-(version-major+minor)
* packages are added so that rust-foo-0.5 is higher than rust-foo-0.4,
  and rust-foo-0.4 inherits from rust-foo-0.5.
* Make sure the versions of the cargo{-development,}-inputs are correct.
  They sometimes change even when bumping a minor version.
* Try to add packages in an order that allows them to be built after
  each commit. This makes it easier to build and lint them.

And make sure at the end that the existing rust packages (currently
rust-cbindgen, ripgrep and librsvg@2.46) continue to build after you've
added and bumped other rust packages.

-- 
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

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2020-01-19 10:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-16  8:14 Rust packaging coordination John Soo
2020-01-18 16:48 ` Martin Becze
2020-01-18 16:55   ` John Soo
2020-01-18 17:20     ` Martin Becze
2020-01-18 17:37       ` John Soo
2020-01-19 10:09   ` Efraim Flashner [this message]
2020-01-21 16:26     ` John Soo
2020-01-27 15:09       ` John Soo
2020-01-30 16:59         ` Martin Becze
2020-01-31 18:45           ` John Soo
2020-02-01 16:05         ` Andreas Rottmann
2020-02-01 18:11           ` John Soo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200119100932.GC1603@E5400 \
    --to=efraim@flashner.co.il \
    --cc=guix-devel@gnu.org \
    --cc=mjbecze@riseup.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).