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.

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

WIP: Add support for --sync #55

Closed
wants to merge 1 commit into from

Conversation

JackWolfard
Copy link

To address #53, this PR adds support for the --sync flag available in cargo vendor.

@JackWolfard
Copy link
Author

@cgwalters What is the testing strategy for this repo? In both cargo itself and the old cargo-vendor crate, the CLI is mocked to allow for testing within the Rust ecosystem, but in this repo, support for doing a similar strategy seems limited.

@cgwalters
Copy link
Member

The current testing code is https://github.com/coreos/cargo-vendor-filterer/blob/main/ci/selftest.sh

In both cargo itself and the old cargo-vendor crate, the CLI is mocked to allow for testing within the Rust ecosystem

That would be nice yes. Hmm, I bet we could lift https://github.com/alexcrichton/cargo-vendor/blob/master/tests/vendor.rs as is indeed.

fn gather_config_from_toml(toml: &Utf8PathBuf, offline: bool) -> Result<Option<VendorFilter>> {
let meta = new_metadata_cmd(toml, offline)
.exec()
.context(format!("Executing cargo metadata for {p} on first run"))?;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think clippy will want with_context instead to only alloc a string on error paths.

@JackWolfard JackWolfard changed the title WIP: Add support for sync pt. 1 WIP: Add support for sync Mar 1, 2023
@JackWolfard JackWolfard changed the title WIP: Add support for sync WIP: Add support for --sync Mar 1, 2023
@JackWolfard
Copy link
Author

Waiting on testing changes from #58 to merge before proceeding with development

@msirringhaus
Copy link
Contributor

@JackWolfard What's your stance on reviving this PR? Do you have any cycles to spare for it?

@JackWolfard
Copy link
Author

JackWolfard commented Mar 5, 2024

@msirringhaus I do not plan on reviving it, as I am no longer actively using the project. Feel free to pickup where I leftoff. Closing the draft.

@JackWolfard JackWolfard closed this Mar 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants