Summary: | Suggestion: remove version specific packages in profiles | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Adam Jannetta <jj10> |
Component: | Enhancement/Feature Requests | Assignee: | Gentoo Release Team <releng> |
Status: | RESOLVED INVALID | ||
Severity: | enhancement | CC: | vapier |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Adam Jannetta
2005-08-09 17:55:17 UTC
Not sure who this goes to...but it's not a portage bug. the versioned packages should be fine, no idea what you're talking about really When a user goes and bootstraps their system the latest stable versions of the packages aren't installed. Instead, the ones specified in the packages file are. that doesnt make any sense, the version strings are '>=' which means everything newer or equal to that version should be utilized Well when I bootstrap my systems, the versions that are installed are the ones listed in the packages file even though >= is used. Really? inertia 2005.1 # cat packages | grep binutils >=sys-devel/binutils-2.15.90.0.3-r4 inertia 2005.1 # pwd /mnt/gentoo/usr/portage/profiles/default-linux/x86/2005.1 inertia log # cat emerge.log | grep binutils 1131021567: *** emerge virtual/os-headers sys-apps/texinfo gettext >=sys-devel/binutils-2.15.90.0.3-r4 >=sys-devel/gcc-3.3.4-r1 virtual/libc >=sys-apps/baselayout-1.11.12-r4 sys-libs/zlib 1131022034: >>> emerge (4 of 8) sys-devel/binutils-2.15.92.0.2-r10 to / 1131022034: === (4 of 8) Cleaning (sys-devel/binutils-2.15.92.0.2-r10::/usr/portage/sys-devel/binutils/binutils-2.15.92.0.2-r10.ebuild) 1131022035: === (4 of 8) Compiling/Merging (sys-devel/binutils-2.15.92.0.2-r10::/usr/portage/sys-devel/binutils/binutils-2.15.92.0.2-r10.ebuild) inertia log # pwd /mnt/gentoo/var/log Looks to me like portage is using the latest stable version. |