All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: James Hilliard <james.hilliard1@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] pkg-rust: new infrastructure
Date: Thu, 6 Jan 2022 22:09:34 +0100	[thread overview]
Message-ID: <20220106220934.24a8ba95@windsurf> (raw)
In-Reply-To: <20210610020632.236282-1-james.hilliard1@gmail.com>

Hello James,

On Wed,  9 Jun 2021 20:06:32 -0600
James Hilliard <james.hilliard1@gmail.com> wrote:

> Add a new infrastructure to ease the development of packages that use
> rust's cargo as their build system.
> 
> Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
> ---
>  package/Makefile.in |   1 +
>  package/pkg-rust.mk | 113 ++++++++++++++++++++++++++++++++++++++++++++
>  2 files changed, 114 insertions(+)
>  create mode 100644 package/pkg-rust.mk

I have re-submitted a new version of the Cargo package infrastructure,
which I had submitted a long time ago. I think it's very close to what
you have done, but also supports vendoring thanks to additional logic,
also shared with the Go package infrastructure.

Could you have a look at the series I just posted?

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2022-01-06 21:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-10  2:06 [Buildroot] [PATCH 1/1] pkg-rust: new infrastructure James Hilliard
2021-06-10 20:11 ` [Buildroot] [External] " Voss, Samuel M Collins
2021-06-12 18:37   ` James Hilliard
2021-06-12 19:23     ` Juergen Stuber
2022-01-06 21:09 ` Thomas Petazzoni [this message]

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

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

  git send-email \
    --in-reply-to=20220106220934.24a8ba95@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@buildroot.org \
    --cc=james.hilliard1@gmail.com \
    /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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.