FreshRSS/rssguard
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Destroyed Download file naming (markdown)

martinrotter 2020-11-09 13:02:41 +01:00
parent 5b047e6f40
commit fb36020317
1 changed files with 0 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
Download-file-naming.md

@ -1,14 +0,0 @@
**Windows builds** of RSS Guard are generated automatically by the tool called AppVeyor. These builds have auto-generated names. In RSS Guard [downloads page](https://github.com/martinrotter/rssguard/releases) you can see filenames like:
* `rssguard-3.4.2-7bad9d1-nowebengine-win32.7z`,
* `rssguard-3.4.2-7bad9d1-win32.7z`,
* `rssguard-3.4.2-95ee6be-nowebengine-win32.exe`,
* `rssguard-3.4.2-95ee6be-win32.exe`.
The structure of these filenames is quite trivial and easily understandable for advanced users. For beginners, the overall structure of the file is `<projectname>-<version>-<commit>-<platform>.<fileformat>`. Example:
* `<projectname>` = `rssguard` (This is self-explanatory.),
* `<version>` = `3.4.2` (This describes the version of the application packaged in the file),
* `<commit>` = `7bad9d1` (This describes the [Git commit](https://git-scm.com/docs/git-commit) used for the file. Whenever developers do some change to source code, that change gets assigned special ID, this is the ID.),
* `<platform>` = `win32` (This is the target platform which the application can run on.),
* `<fileformat>` = `exe` (This is self-explanatory.).
Note that same file naming scheme is used for auto-generated builds for Linux and Mac OS.