Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Tracking Issue: Support project-specific config in manifest #12738

Open
5 tasks
epage opened this issue Sep 26, 2023 · 0 comments
Open
5 tasks

Tracking Issue: Support project-specific config in manifest #12738

epage opened this issue Sep 26, 2023 · 0 comments
Labels
A-configuration Area: cargo config files and env vars A-manifest Area: Cargo.toml issues C-tracking-issue Category: A tracking issue for something unstable.

Comments

@epage
Copy link
Contributor

epage commented Sep 26, 2023 •
edited
Loading

Configuration is for the environment a package is being built in. Through experience, we find that some environment concerns are actually package concerns and users run into problems with them being tied into the environment.

This is meant to track configuration that should be supported in manifests. This won't always be a one-to-one mappings.

See also
@epage epage added A-configuration Area: cargo config files and env vars A-manifest Area: Cargo.toml issues C-tracking-issue Category: A tracking issue for something unstable. labels Sep 26, 2023
@epage epage mentioned this issue Sep 28, 2023
Open
This was referenced Nov 3, 2023
Closed
Open
Open
@weihanglo weihanglo mentioned this issue Feb 1, 2024
Closed
@epage epage mentioned this issue Apr 22, 2024
Merged
@epage epage mentioned this issue Jun 3, 2024
Open
@ppannuto ppannuto mentioned this issue Jul 2, 2024
Closed
2 tasks
@weihanglo weihanglo mentioned this issue Jul 6, 2024
Closed
@epage epage mentioned this issue Jul 13, 2024
Open
@epage epage mentioned this issue Aug 17, 2024
Closed
@epage epage mentioned this issue Sep 9, 2024
Open
6 tasks
@epage epage mentioned this issue Sep 18, 2024
Open
@dsabala dsabala mentioned this issue Oct 30, 2024
Closed
uncomfyhalomacro added a commit to openSUSE-Rust/obs-service-cargo that referenced this issue Nov 17, 2024
@uncomfyhalomacro
improvements: parent path of Cargo.toml files are now set as current …
d3354d8 
…directory when invoking commands

This is to address this weird issue in
rust-lang/cargo#10302.

Related issues about `cargo` improvements are tracked here in
rust-lang/cargo#12738.

Currently, to do this manually, it must be set to the parent path
of Cargo.toml.

Signed-off-by: Soc Virnyl Estela <contact@uncomfyhalomacro.pl>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-configuration Area: cargo config files and env vars A-manifest Area: Cargo.toml issues C-tracking-issue Category: A tracking issue for something unstable.
Projects
Cargo Roadmap
Archived in project
Milestone
No milestone
Development

No branches or pull requests
1 participant
@epage