As Petri Kaukasoina pointed out, my hypothetical example with python-2 was badly chosen (should have used mesa instead). Also a reminder that every 14.1, 14.2, and current packages cannot be found in the cumulative repo.
However, if used with afterthought (e.g. by carefully checking package names in the appropriate Changelog file), the worst that could happen is realising that the sought-for package can't be found. And should you make a mistake, such as downgrading a non-functional python-2.7.17-x86_64-1_slack14.2.txz to python-2.7.16-x86_64-1.txz (which also will be non-functional but for different reasons), no new breaks will occur so you won't be worse off than before.
With afterthought, it's also a good idea not to use automatic tools for upfrading kernel-* packages.
|