From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Christian Stewart <christian@paral.in>
Cc: Anisse Astier <anisse@astier.eu>,
"Yann E . MORIN" <yann.morin.1998@free.fr>,
Buildroot Mailing List <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH-NEXT v3 1/6] support/download/dl-wrapper: add concept of download post-processing
Date: Thu, 14 Oct 2021 23:15:04 +0200 [thread overview]
Message-ID: <20211014231504.3fbfc964@windsurf> (raw)
In-Reply-To: <CA+h8R2pf-df3MF1z5Rgi1ez5i1FBUDBiPh4R=CvzKqynBaeddg@mail.gmail.com>
Hello Christian,
On Mon, 11 Oct 2021 00:13:02 -0700
Christian Stewart <christian@paral.in> wrote:
> > - The initial series also had support for Cargo, I think we want to
> > retain that as the idea was to solve both Go and Cargo at the same
> > time, to make sure we have a solution that works for both.
>
> I don't have the experience with Rust to sign off on the Cargo
> portion, and I was unsure if it was confirmed to be ready for merging.
> So in the interest of getting these packages in (including gocryptfs)
> I sent the Go portion only.
When I sent the series, I had neither the experience with Go nor Rust :-)
> Can send the full thing with the Cargo as well... if really necessary,
> but can't we just do it in 2 patch series?
The idea of having a single series was to make sure we are able to
implement a mechanism that works (at least) for two different
vendoring-based package management systems.
> > - PATCH-NEXT doesn't make any sense right now, there is no "next"
> > branch.
>
> Ok, was just indicating that it's somewhat "next release" material
> (not for backport), I guess.
Whether something is to be considered for backport or not is a decision
that Peter Korsgaard does. And new features are by nature generally not
considered for backporting.
Cheers!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-10-14 21:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-10 23:46 [Buildroot] [PATCH-NEXT v3 1/6] support/download/dl-wrapper: add concept of download post-processing Christian Stewart via buildroot
2021-10-10 23:46 ` [Buildroot] [PATCH-NEXT v3 2/6] package/pkg-download.mk: add <pkg>_DOWNLOAD_POST_PROCESS variable Christian Stewart via buildroot
2021-10-10 23:46 ` [Buildroot] [PATCH-NEXT v3 3/6] support/download/post-process-helpers: add helper function for post process scripts Christian Stewart via buildroot
2021-10-10 23:46 ` [Buildroot] [PATCH-NEXT v3 4/6] support/download/go-post-process: implement Go vendoring support Christian Stewart via buildroot
2022-01-06 10:32 ` Thomas Petazzoni
2022-01-06 21:08 ` Thomas Petazzoni
2022-01-06 21:20 ` Christian Stewart via buildroot
2022-01-07 0:45 ` Christian Stewart via buildroot
2021-10-10 23:46 ` [Buildroot] [PATCH-NEXT v3 5/6] package/embiggen-disk: new package Christian Stewart via buildroot
2021-10-10 23:46 ` [Buildroot] [PATCH-NEXT v3 6/6] package/gocryptfs: " Christian Stewart via buildroot
2021-10-11 7:04 ` [Buildroot] [PATCH-NEXT v3 1/6] support/download/dl-wrapper: add concept of download post-processing Thomas Petazzoni
2021-10-11 7:13 ` Christian Stewart via buildroot
2021-10-14 21:15 ` Thomas Petazzoni [this message]
2022-01-06 21:05 ` Thomas Petazzoni
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=20211014231504.3fbfc964@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=anisse@astier.eu \
--cc=buildroot@buildroot.org \
--cc=christian@paral.in \
--cc=yann.morin.1998@free.fr \
/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.