Summary: | "emerge -pvuD --usepkg mplayer" offers different packages than "emerge -pvuD mplayer" | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | csights |
Component: | Current packages | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
csights
2005-03-03 06:22:08 UTC
*** Bug 83961 has been marked as a duplicate of this bug. *** Try using --tree. This is not a bug, it's a feature. Try adding --newuse to your flags. I have updated the packages and would have to uninstall in order to see what --newuse and --tree would do. What should I look for next time? I don't see any * on the USE flags for the packages being emerged. How would --newuse change anything? Maybe you confusing -K (usepkgonly) with -k (usepkg)? From the emerge man page: "--usepkg (-k) Tells emerge to use binary packages (from $PKGDIR) if they are available, ..." This leads to an expectation that emerge will download source if the binary packages aren't available. E.g. ________________________________________ emerge -pvuD --usepkg mplayer These are the packages that I would merge, in order: Calculating dependencies ...done! [binary U ] sys-kernel/linux-headers-2.4.22-r1 [2.4.21-r1] -build 0 kB [ebuild N ] media-libs/libdvdcss-1.2.8 -doc -static 204 kB [ebuild N ] media-libs/libdvdread-0.9.4 250 kB ___________________________________________________________________________ rather than what actually happens: ___________________________________ emerge -pvuD --usepkg mplayer These are the packages that I would merge, in order: Calculating dependencies ...done! [binary U ] sys-kernel/linux-headers-2.4.22-r1 [2.4.21-r1] -build ___________________________________________________________________________ This is the result I expect from -K (usepkgonly) |