From: orbea <orbea@riseup.net>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH] cargo.eclass: add CARGO_TOML_DIR
Date: Tue, 23 Jan 2024 06:11:21 -0800 [thread overview]
Message-ID: <20240123061121.3197c162@Akita> (raw)
In-Reply-To: <2d38f358-bf12-4818-b952-dd27f8fe7a42@gmail.com>
On Mon, 22 Jan 2024 23:06:35 -0500
Eli Schwartz <eschwartz93@gmail.com> wrote:
> On 1/22/24 10:32 PM, orbea wrote:
> > This is required when cargo_live_src_unpack needs to be find a
> > Cargo.toml file in a directory other than ${S}
> >
> > Signed-off-by: orbea <orbea@riseup.net>
> > ---
>
>
> Fairly confused why this email was posted to an existing thread
> instead of a new one?
>
> Anyway, I'm sure the change is very reasonable but it is difficult to
> tell from an outside perspective just by reading the commit message --
> which doesn't detail why your Cargo.toml would be in a directory other
> than the one src_compile() starts off in.
>
>
My mistake in composing the e-mail in why it was posted to an existing
thread.
The program in question is:
https://github.com/Rosalie241/RMG
Which has an optional rust plugin.
https://github.com/Rosalie241/RMG/tree/master/Source/3rdParty/mupen64plus-input-gca
It seems impossible to support a live ebuild unless
cargo_live_src_unpack knows where to look.
prev parent reply other threads:[~2024-01-23 14:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-22 16:14 [gentoo-dev] [PATCH] profiles: workaround sandbox bug with getcwd() configure test (gl_cv_func_getcwd_path_max) Sam James
2024-01-22 16:35 ` David Seifert
2024-01-22 16:45 ` [gentoo-dev] " Arsen Arsenović
2024-01-23 3:32 ` [gentoo-dev] [PATCH] cargo.eclass: add CARGO_TOML_DIR orbea
2024-01-23 3:48 ` Michał Górny
2024-01-23 14:13 ` orbea
2024-01-23 16:48 ` Michał Górny
2024-01-23 19:43 ` orbea
2024-01-24 18:59 ` orbea
2024-01-23 4:06 ` Eli Schwartz
2024-01-23 14:11 ` orbea [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=20240123061121.3197c162@Akita \
--to=orbea@riseup.net \
--cc=gentoo-dev@lists.gentoo.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