On Jan 26 11:20, Achim Gratz wrote: > Corinna Vinschen writes: > > What if the "test" version gets removed, without updating "curr"? > > Then there presumably was a good reason to pull that test version. > > > What would make more(?) sense is sticking to "installed" instead, > > because the version number is higher than the "curr" version. This > > behaviour would reflect the behaviour of `yum update'. > > With test releases that get pulled I think it really is correct that the > default reverts back to "curr".
Really? Here's what I'm doing on Linux: The latest upstream release 1.24 adds a feature I need. The official package version 1.23-44 is obviously still missing this feature, so I build my own rpm with the upstream version 1.24-0 and install that: Official: 1.23-44 Installed: 1.24-0 The official package gets updated to 1.23-47. What I'm expecting now is that the update does NOT update my package, and that's what yum or apper will do. They will leave my higher version alone: Official: 1.23-47 Installed: 1.24-0 Now the official version is pulled up to the next upstream version. The new package is 1.24-3. This time the version number is higher, so yum or apper will update: Official: 1.24-3 Installed: 1.24-3 Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat
pgpD7JrBK7XoP.pgp
Description: PGP signature