You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem
Actually, you can create a lib or a bin where the package contains files such as aux.rs which have Windows reserved filenames.
As soon as #8055 is closed, cargo will display a proper error when you try to unpack these types of packages.
But it actually doesn't say anything to the user when you try to build/publish a crate.
Obviously, you maybe are not building your package to be ran in Windows but Linux, and then this is not an issue at all.
But maybe it should at least make the user know that if he is targeting Windows as an OS where the package is going to be deployed, using windows reserved filenames will make the package impossible to install or run.
Imo it will be so annoying to have a warning on build level. Even something like #![allow(windows_reserved_filenames)] will do the job. But again, seems too much to me.
I don't know if that makes sense from the teams perspective, but the previous issue made me think that if we will error when we find that filenames, we should then advise users before publishing.
The text was updated successfully, but these errors were encountered:
CPerezz
changed the title
Cargo should warn/suggest you when you build or publish a crate have files with with windows reserved filenames
Cargo warning when you try to publish a crate that contains files/folders with windows reserved filenames
Apr 26, 2020
It was only implemented a few weeks ago in #7959. It takes anywhere from 6 to 12 weeks for changes to make it to stable. You can also check the CHANGELOG, which is updated once every 6 weeks.
Problem
Actually, you can create a lib or a bin where the package contains files such as
aux.rs
which have Windows reserved filenames.As soon as #8055 is closed, cargo will display a proper error when you try to unpack these types of packages.
But it actually doesn't say anything to the user when you try to build/publish a crate.
Obviously, you maybe are not building your package to be ran in Windows but Linux, and then this is not an issue at all.
But maybe it should at least make the user know that if he is targeting Windows as an OS where the package is going to be deployed, using windows reserved filenames will make the package impossible to install or run.
Possible Solution(s)
#![allow(windows_reserved_filenames)]
will do the job. But again, seems too much to me.I don't know if that makes sense from the teams perspective, but the previous issue made me think that if we will error when we find that filenames, we should then advise users before publishing.
The text was updated successfully, but these errors were encountered: