@mrmarkuz, @giacomo: It is not possible to have nethserver-nextcloud package version linked to Nextcloud version?
Example: nethserver-nextcloud-1.22.x-1.ns7.noarch.rpm based on Nextcloud 22.x?
Currently nethserver-nextcloud-1.17.1-1.ns7.noarch.rpm is based on Nextcloud 21.0.3.
It is not Nextcloud 17.1…
That’s not possible because every fix raises the nethserver-nextcloud version too.
In my example: nethserver-nextcloud-1.22.x-X.ns7.noarch.rpm:
First build for 22.0.0: nethserver-nextcloud-1.22.0.0-1.ns7.noarch.rpm
Second build for 22.0.0: nethserver-nextcloud-1.22.0.0-2.ns7.noarch.rpm
I don’t think it’s worth the effort. To be consistent we’d need it for other apps too (roundcube, mattermost, etc.) but they may have different versionings.
IMO the advantage is minimal. You can check app versions in the different web UIs or on command line.
Some time ago @giacomo has maintened a rpm of nextcloud itself but the community of nextcloud did not raise effort to help nor to be interested to really use it. It ends that this rpm has been discontinued.
Darwin theory is not only for the evolution of species but also for softwares
Bigger difference among Darwin’s law and software development is humans. Sometimes are dumb.
Not so much I think, when a specy reachs the end of its evolution, it just disapears.
Like neanderthal 30 000 years ago.
You must be adaptable or disapear