External Publication
Visit Post

[Pre-RFC] `cargo package` should include fewer files by default

Rust Internals [Unofficial] April 26, 2026
Source
I am aware that you linked to the issue (and everything that is linked and cited from there) to draw attention to the bigger picture and all the conversations that happened around licenses/license files. As you mentioned, it is important to have these conversations in mind and I went through them without limiting myself on information that deals with the specific issue I've linked in my post again. I just included it because you mentioned before that there was a decision in the Cargo team to not use globs for license files. epage: > To me, a strong reason would be needed to bypass this [decision] and have a glob for LICENSE files. Yet this discussion happened for a very different use case, as I was trying to make clear in my post you replied to. I spent the first part of my post to go into detail on this issue because I got the impression that this specific detail is currently considered to be a blocker for the changes layed out in this Pre RFC. The rest of the post deals with the general relationship between the issue of workspace-licenses and this Pre RFC and how I think they can exist separately. I've tried to discuss how making a decision here would not affect or limit the possibilities for a future solution of the workspace-license issue. I've included why I think a glob-based license file matching fits in the current state of workspace licenses and would be a reasonable approach to figure out which license files to include in a crate by default. Do you think my post is going in the direction of analyzing overlaps in use case and design or would you wish for something else in that regard? I don't claim to have covered every detail, but in my opinion, it should at least be a good start to compare both issues.

Discussion in the ATmosphere

Loading comments...