On 2021/02/19 06:00, Dominique Leuenberger / DimStar wrote:
This comes from openSUSE 10.2 - which was released in 2006; so 15 years
ago. The package installs just fine - and runs.
No -- we are talking about rpm. So install rpm from 10.2 and
use it to install + upgrade from the current rpm-sources using
the rpmbuild in 10.2.
Might help if you use the same product.
The rpm I have doesn't read the rpm's in the new compressed
encoding. Would it have been that painful to have rpm that you ship today
be installable on any tumbleweed system by statically linking it?
Then someone can upgrade to some distro-specific-recoded rpm after
that. Just having a cutoff at >=4.15 = only rpm that will read new
rpm-formats, while <4.15 can't install 4.15 sorta sucks.
People think shared libs are the answer because of security fixes, but
not every program links with every lib. Furthermore, there are programs
that are alot more useful to have "working" than worry about patching for
a security fix that might happen once in a blue moon. If rpm needs a
security fix, create 1 new static rpm that works everywhere.
This is a problem -- creating static programs for things being able to
open your rpm's old+new, is 1 program. Same might be true for a boot
shell and 'mount'. Somethings are more important than being
fragile and subject to not running on a system w/different libs or
a different installation encoding.