Add an explicit include section to the Cargo.toml
#222
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This commit adds an explicit `package.include` section to the `Cargo.toml` file to only include relevant rust code into the final package. This decreases the size of the uploaded tar-ball from 1.3 Mb to ~700kb and it also decreases the number of included files from ~140 to ~70. Finally it removes any possibly unwanted binary data from the uploaded package, which follows security best-practices. Fixes dropbox#220
|
|
|
@danielrh Mind having a look at this? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit adds an explicit
package.includesection to theCargo.tomlfile to only include relevant rust code into the final package. This decreases the size of the uploaded tar-ball from 1.3 Mb to ~700kb and it also decreases the number of included files from ~140 to ~70. Finally it removes any possibly unwanted binary data from the uploaded package, which follows security best-practices.Fixes #220