| View previous topic :: View next topic |
| Author |
Message |
creaker
l33t
Joined: 14 Jul 2012
Posts: 651
|
 Posted: Thu Aug 29, 2013 7:33 pm Post subject: How does emerge selects package to install? |
 |
|
Currently I have three ebuilds under kde-base/kdelibs:
4.10.5-r1
4.11.0-r1
4.11.0
On emerge -pv kdelibs I getting a message that the 4.10.5-r1 will be installed.
Why it is not a 4.11.0 or 4.11.0-r1? Does emerge installs the oldest of available packages or it is selected for some other reasons? |
|
| Back to top |
|
 |
eccerr0r
Watchman
Joined: 01 Jul 2004
Posts: 9677
Location: almost Mile High in the USA
|
| Posted: Thu Aug 29, 2013 7:48 pm Post subject: |
|
|
No, portage will favor the highest version that aren't "masked" that solves all dependencies in satisfying what you're trying to emerge.
The 4.11 versions are keyworded as "unstable" meaning it has not been fully tested:
KEYWORDS="~amd64 ~arm ~ppc ~ppc64 ~x86 ~amd64-fbsd ~x86-fbsd ~amd64-linux ~x86-linux"
but assumed to work OK hence it even has a keyword. To use these versions you need to accept the "~" unstable version by adding an exception to /etc/portage/package.accept_keywords. See "man portage" and look for package.accept_keywords for more info.
One possible result would be to add something like "kde-libs/kdelibs ~* *" to /etc/portage/package.accept_keywords to be architecture agnostic.
_________________
Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD
What am I supposed watching? |
|
| Back to top |
|
|
Navar
Guru
Joined: 20 Aug 2012
Posts: 353
|
| Posted: Thu Aug 29, 2013 8:07 pm Post subject: |
|
|
Roughly, in layman's terms, ignoring the 13+ other special cases someone will bring up...
| Code: |
$ equery l -p kde-base/kdelibs
* Searching for kdelibs in kde-base ...
[-P-] [ ] kde-base/kdelibs-4.10.5-r1:4
[-P-] [ ~] kde-base/kdelibs-4.11.0:4
[-P-] [ ~] kde-base/kdelibs-4.11.0-r1:4
|
- 1. Version dependencies from other packages installed or being installed.
- 2. Use flag differences/dependencies between versions (this can vary between ebuild revision or just update of existing).
- 3. arch keywording, ~ or non (somewhat same as #2).
- 4. Often upgrading to newest version given keywording qualifier restriction.
Exception to #4 is when you've emerged a specific version of a package or --oneshot installing to avoid the package being in your world file for further updates.
_________________
Ph'nglui mglw'nafh Cthulhu R'lyeh wgah'nagl fhtagn. |
|
| Back to top |
|
|
creaker
l33t
Joined: 14 Jul 2012
Posts: 651
|
| Posted: Thu Aug 29, 2013 9:40 pm Post subject: |
|
|
Thanks for replies!
It's clear, if I want stable 4.11.0, I have to wait. Right now 4.11.0 pulls in a lot of masked packages. |
|
| Back to top |
|
|
|
Portage & Programming
