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

Remove all Cargo.toml files from spec.extensions #245

Merged
merged 1 commit into from
Aug 3, 2023

Conversation

Youssef-Mak
Copy link
Contributor

All */Cargo.(toml|lock) files should be removed from spec.extensions.

@Youssef-Mak Youssef-Mak marked this pull request as draft July 28, 2023 21:03
@Youssef-Mak Youssef-Mak force-pushed the patch-1 branch 3 times, most recently from f5c2256 to ba7fee5 Compare July 28, 2023 21:28
@@ -45,6 +45,7 @@ def init(name = nil, gem_spec = nil)
gemspec.files.reject! { |f| f.end_with?(".rs") }
gemspec.files.reject! { |f| f.match?(/Cargo.(toml|lock)$/) }
gemspec.files.reject! { |f| extconf.end_with?(f) }
gemspec.extensions.reject! { |f| f.end_with?("Cargo.toml") }
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Should we also consider Cargo.lock here?

Copy link
Collaborator

Choose a reason for hiding this comment

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

I think this is good, since rubygems will deny any Cargo.lock anyway.

@Youssef-Mak Youssef-Mak requested a review from ianks August 1, 2023 16:19
@Youssef-Mak Youssef-Mak marked this pull request as ready for review August 1, 2023 16:19
@Youssef-Mak Youssef-Mak changed the title Remove all Cargo.(lock|toml) files from spec.extensions Remove all Cargo.toml files from spec.extensions Aug 1, 2023
@ianks
Copy link
Collaborator

ianks commented Aug 3, 2023

🙇🏻

@ianks ianks merged commit e733fd6 into oxidize-rb:main Aug 3, 2023
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.

2 participants