Hello,
I have created a small distribution for a custom platform.
Because I am cross compiling all packages, auto dependencies are not possible, so I define dependencies manually.
I created a package with version 1.00preX. After the preX series, release candidate was out, so I named the new package(s) 1.00rcX. Now the final version has come out, which is named 1.00.
When I created the package 1.00 all hell broke loose.
If I install package 1.00, all the packages with:
requires: foobar >= 1.00preX or requires: foobar >= 1.00rcX
report dependency errors.
In the past I noticed that RPM was able to resolve that:
1.00rc3 > 1.00rc2 > 1.00rc1 > 1.00pre8 > 1.00pre7 > ...
But now it assumes that 1.00XX > 1.00
Unfortunately, this is a core package and almost everything depends on it. Is there a way to overcome this without rebuilding the entire distribution?
I also want to distinguish between the 1.00 version and all previous versions, because some packages must have explicit dependency to 1.00 (and *not* be able to install if 1.00preX or 1.00rcX are installed).
One hack I tried that solved this problem was to "rename" the stable version to "1.00rc4" (the rc series stopped at rc3). But this is not a pretty way to solve this...
-- Manousaridis Angelos
_______________________________________________ Rpm-list mailing list Rpm-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/rpm-list
