If my understanding is right, OpenSUSE Tumbleweed isn't exactly a rolling release correct? It is creating a snapshot at regular intervals (weekly? Or monthly) and NOT updating packages which have updates.
This means irrespective of you having only updates for 100 packages, it will update all your 1500 packages (Or the number of packages that you have installed on the system).
Can someone confirm this? Because if this is true, that is such a waste.
The reason TW has big 1500-package updates is not because of any snapshotting. It's because TW's automation defensively bumps the release number of reverse dependencies. So if libfoo is updated then all reverse dependencies of libfoo are also updated, regardless of whether the libfoo update was ABI-compatible or not.
In Alpine for example, the maintainers only bump rdepends when they think those need to be rebuilt, which sometimes leads to them underestimating and those unupdated rdepends end up breaking. TW avoids that but at the cost of a lot of "pointless" updates.
That is not at all true, Tumbleweed often updates as often as daily and only the packages that need to be updated are updated outside of the rare case of a new glib version where everything has to rebuilt and all packages are indeed updated.
Comments
If my understanding is right, OpenSUSE Tumbleweed isn't exactly a rolling release correct? It is creating a snapshot at regular intervals (weekly? Or monthly) and NOT updating packages which have updates.
This means irrespective of you having only updates for 100 packages, it will update all your 1500 packages (Or the number of packages that you have installed on the system).
Can someone confirm this? Because if this is true, that is such a waste.
The reason TW has big 1500-package updates is not because of any snapshotting. It's because TW's automation defensively bumps the release number of reverse dependencies. So if libfoo is updated then all reverse dependencies of libfoo are also updated, regardless of whether the libfoo update was ABI-compatible or not.
In Alpine for example, the maintainers only bump rdepends when they think those need to be rebuilt, which sometimes leads to them underestimating and those unupdated rdepends end up breaking. TW avoids that but at the cost of a lot of "pointless" updates.
Thank you. That clears a lot of things.
That is not at all true, Tumbleweed often updates as often as daily and only the packages that need to be updated are updated outside of the rare case of a new glib version where everything has to rebuilt and all packages are indeed updated.