[ZBXNEXT-3730] have a major version symlinked to its latest minor version release in the repo Created: 2017 Mar 02 Updated: 2017 Mar 07 Resolved: 2017 Mar 07 |
|
| Status: | Closed |
| Project: | ZABBIX FEATURE REQUESTS |
| Component/s: | Installation (I) |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Change Request | Priority: | Trivial |
| Reporter: | coolfire | Assignee: | Unassigned |
| Resolution: | Won't fix | Votes: | 0 |
| Labels: | repo, symlinks | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Please, for existing versions and whenever a new minor version is released under a major version, create a symlink to it with major version name. For example, 3.2 is current stable and there could be 3 -> 3.2, when 3.3 released, 3 -> 3.3 and when 4.0 released, 4 -> 4.0 etc. This gives SysAdmins feasibility of not to change repo files for every minor release. |
| Comments |
| Comment by richlv [ 2017 Mar 02 ] |
|
actually, the second number in the version is not really minor version. not only such versions have large changes, they are also mostly incompatible and have different support conditions. for example, server and proxy must be at the same major version (where 3.0 and 3.2 are different major versions). linking 3 to 3.x should not be done. |
| Comment by Kodai Terashima [ 2017 Mar 03 ] |
|
I agree with richlv, the second number is major version. creating symlink leads unexpected upgrading process. |