Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Matt Madison <matt@madison.systems>
To: openembedded-core@lists.openembedded.org
Cc: Joshua Watt <jpewhacker@gmail.com>, Matt Madison <matt@madison.systems>
Subject: [OE-core][PATCH 3/4] cargo_common.bbclass: remove inherit of crate-fetch
Date: Fri, 17 Dec 2021 07:36:29 -0800	[thread overview]
Message-ID: <20211217153630.1746217-4-matt@madison.systems> (raw)
In-Reply-To: <20211217153630.1746217-1-matt@madison.systems>

No longer needed now that the crate fetcher is
installed via OE_IMPORTS.

Signed-off-by: Matt Madison <matt@madison.systems>
---
 meta/classes/cargo_common.bbclass | 2 --
 1 file changed, 2 deletions(-)

diff --git a/meta/classes/cargo_common.bbclass b/meta/classes/cargo_common.bbclass
index 23d82aa6ab..c403591434 100644
--- a/meta/classes/cargo_common.bbclass
+++ b/meta/classes/cargo_common.bbclass
@@ -8,8 +8,6 @@
 ## is used by cargo.bbclass and Rust
 ##
 
-# add crate fetch support
-inherit crate-fetch
 inherit rust-common
 
 # Where we download our registry and dependencies to
-- 
2.32.0



  parent reply	other threads:[~2021-12-17 15:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-17 15:36 [OE-core][PATCH 0/4] Move crate fetcher to OE_IMPORTS Matt Madison
2021-12-17 15:36 ` [OE-core][PATCH 1/4] lib/crate.py: install crate fetcher on import Matt Madison
2021-12-17 15:36 ` [OE-core][PATCH 2/4] base.bbclass: add crate to OE_IMPORTS Matt Madison
2021-12-17 16:37   ` Alexander Kanavin
2021-12-20 15:34     ` Matt Madison
2021-12-17 15:36 ` Matt Madison [this message]
2021-12-17 15:36 ` [OE-core][PATCH 4/4] classes: remove crate-fetch.bbclass Matt Madison
2021-12-20 17:01 ` [OE-core][PATCH 0/4] Move crate fetcher to OE_IMPORTS Paul Barker
2021-12-20 22:34   ` Richard Purdie
2021-12-21 14:07     ` Paul Barker
2021-12-21 18:14       ` Matt Madison
     [not found]       ` <16C2D7CF44733347.22520@lists.openembedded.org>
2022-01-14 10:31         ` Matt Madison
2022-01-14 13:17           ` Richard Purdie

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=20211217153630.1746217-4-matt@madison.systems \
    --to=matt@madison.systems \
    --cc=jpewhacker@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox