| Summary: | virtual/bitcoin-leveldb should list highest versioned dependencies first | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Taahir Ahmed <ahmed.taahir> |
| Component: | [OLD] Unspecified | Assignee: | Anthony Basile <blueness> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | ahmed.taahir, luke-jr+gentoobugs, proxy-maint, qa |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
The whole point of the virtual is that they are bug-for-bug compatible, so none should be preferred over the other really. We can reorder this... Okay, sounds good. Thanks! Portage just installed 1.9.0* for me, for no apparent reason. Care to finally reorder this? Reordered. |
virtual/bitcoin-leveldb uses an || dependency to collect versions of leveldb that are suitable for use with bitcoind: || ( =dev-libs/leveldb-1.9.0-r6[-snappy] =dev-libs/leveldb-1.10.0-r1[-snappy] =dev-libs/leveldb-1.11.0-r1[-snappy] =dev-libs/leveldb-1.12.0-r1[-snappy] =dev-libs/leveldb-1.13.0-r1[-snappy] =dev-libs/leveldb-1.14.0-r1[-snappy] =dev-libs/leveldb-1.15.0-r1[-snappy] ) Is it really the case that the lower version numbers are the most preferable? If not, the atoms inside the || block should be listed in descending order of version. This is causing some minor problems with a system-wide update using cave --- cave is wanting to hang on to the older version of leveldb and is asking for an override to do so. It's not a big deal, but I thought I would check to be sure that this really is the desired behavior. Reproducible: Always