If a build script for a library downloads a file conflicts can happen which will prevent the download from happening. If a file with the same filename as the filename of the download already exists, the download will not happen. This can cause problems later on with the way Github names tar archives for tags.
If you want to add a library and release version 1.1 on Github, the source download will be 1.1.tar.gz currently. This is too generic for our purposes.
I'm thinking of making the download function add the library name to the filename if it isn't already in there. Then instead of 1.1.zip, the file would be saved as library-1.1.zip. Any opinions on this?
If a build script for a library downloads a file conflicts can happen which will prevent the download from happening. If a file with the same filename as the filename of the download already exists, the download will not happen. This can cause problems later on with the way Github names tar archives for tags.
If you want to add a library and release version 1.1 on Github, the source download will be 1.1.tar.gz currently. This is too generic for our purposes.
I'm thinking of making the download function add the library name to the filename if it isn't already in there. Then instead of 1.1.zip, the file would be saved as library-1.1.zip. Any opinions on this?