File types to exclude from packages
Permalink
What files types do you have within package directories on your development system that should not be included in a marketplace package zip?
For example, .sh shell scripts, Thumbs.db, etc.
(This is for some automated package checking I am working on).
For example, .sh shell scripts, Thumbs.db, etc.
(This is for some automated package checking I am working on).
Thanks. I have a blanket catch-all on .dot files and will extend that to make sure .dot directories are also excluded.
Any thoughts on directory names beginning with _ ? I currently have checks on __MACOSX, but could/should that be more general?
Any thoughts on directory names beginning with _ ? I currently have checks on __MACOSX, but could/should that be more general?
Given how C5 works, I don't see anything starting with an underscore being part of the package. Could be notes but most likely for the dev usage.
C5 will look for a CHANGELOG file but that's about it.
Then again, this kind of naming convention could be used for CSS or JS files so you never know.
But aren't you planning on making it a setting so edgy inclusion and exclusions could be customized?
C5 will look for a CHANGELOG file but that's about it.
Then again, this kind of naming convention could be used for CSS or JS files so you never know.
But aren't you planning on making it a setting so edgy inclusion and exclusions could be customized?
Yes, all settings for validation on upload and filtering on package building can be enabled and disabled, and I have *glob* pattern matching for anything user specific, but I also want to provide convenient options for common cases, such as .dot files etc. already enabled.
Hence this open forum-brainstorming for specific file and directory types and patterns. There could be unwanted files generated by environments or code editors in common use (but I don't use) that could usefully be built into my tools.
Hence this open forum-brainstorming for specific file and directory types and patterns. There could be unwanted files generated by environments or code editors in common use (but I don't use) that could usefully be built into my tools.
ok. So I gave you what I have. There's a good website you can use. It gives you typical .gitignore configuration for different OS and apps. For instance, PHPstorm generates .idea files and Windows generates Desktop.ini files
The website is:http://www.gitignore.io/
You'll get lots of usable stuff there
The website is:http://www.gitignore.io/
You'll get lots of usable stuff there
Great resource and you have inspired some neat ideas.
I just did a bit of edit-fu on it and there are 3536 different patterns, some of which are spurious, some of which would be caught by rules I already have, and many that I can't see ever needing to be part of a distributed package.
Rather than make sense of the whole lot, I am thinking of a v2 Package Magic (ie. not the current version) that could look at a .gitignore, exclude it, and use the definitions within .gitignore for managing exclusions when building a package archive.
I just did a bit of edit-fu on it and there are 3536 different patterns, some of which are spurious, some of which would be caught by rules I already have, and many that I can't see ever needing to be part of a distributed package.
Rather than make sense of the whole lot, I am thinking of a v2 Package Magic (ie. not the current version) that could look at a .gitignore, exclude it, and use the definitions within .gitignore for managing exclusions when building a package archive.
sounds like you're having lots of fun with that ;)
I am using VS Code as an editor so .vscode folders as well
I'd say probably anything that starts with a dot should be removed.